#POSTGRESQL CAST INTEGER TO TEXT HOW TO#
#POSTGRESQL CAST INTEGER TO TEXT CODE#

Note that when ANALYZE option is used, the summary information is included by default. The SUMMARY parameter adds summary information such as total timing after the query plan. The TIMING defaults to TRUE and it may only be used when ANALYZE is enabled. This parameter includes the actual startup time and time spent in each node in the output. By default, the BUFFERS parameter set to FALSE. BUFFERS only can be used when ANALYZE is enabled. This parameter adds information to the buffer usage. The COSTS option includes the estimated startup and total costs of each plan node, as well as the estimated number of rows and the estimated width of each row in the query plan. The VERBOSE parameter allows you to show additional information regarding the plan. The ANALYZE statement actually executes the SQL statement and discards the output information, therefore, if you want to analyze any statement such as INSERT, UPDATE, or DELETE without affecting the data, you should wrap the EXPLAIN ANALYZE in a transaction, as follows: BEGIN The ANALYZE option causes the sql_statement to be executed first and then actual run-time statistics in the returned information including total elapsed time expended within each plan node and the number of rows it actually returned. If you omit the boolean, it defaults to ON.

You can use TRUE, ON, or 1 to enable the option, and FALSE, OFF, or 0 to disable it. The boolean specifies whether the selected option should be turned on or off.

#POSTGRESQL CAST INTEGER TO TEXT CODE#

Where option can be one of the following: ANALYZE įORMAT Code language: JavaScript ( javascript ) The following shows the syntax of the EXPLAIN statement: EXPLAIN ) ] sql_statement Code language: CSS ( css ) The most important and useful information that the EXPLAIN statement returns are start-cost before the first row can be returned and the total cost to return the complete result set. The EXPLAIN shows how tables involved in a statement will be scanned by index scan or sequential scan, etc., and if multiple tables are used, what kind of join algorithm will be used. The EXPLAIN statement returns the execution plan which PostgreSQL planner generates for a given statement. Introduction to PostgreSQL EXPLAIN statement

#POSTGRESQL CAST INTEGER TO TEXT HOW TO#

Summary: in this tutorial, you have learned how to use the PostgreSQL EXPLAIN statement to display the execution plan of a statement.

Postgresql cast integer to text