Make better use of ParseState in ProcessUtility
authorPeter Eisentraut <peter@eisentraut.org>
Sat, 4 Jan 2020 10:56:58 +0000 (11:56 +0100)
committerPeter Eisentraut <peter@eisentraut.org>
Sat, 4 Jan 2020 12:12:41 +0000 (13:12 +0100)
commit3fd40b628c7db4c4bcf03b548f9a55f85e327e25
tree5db105f66b7f6b3fd753e8d43abc0455d7e25dbe
parentd2e5e20e57111cca9e14f6e5a99a186d4c66a5b7
Make better use of ParseState in ProcessUtility

Pass ParseState into the functions called from
standard_ProcessUtility() instead passing the query string and query
environment separately.  No functionality change, but it makes the
notation consistent.  We had already started moving things into
that direction piece by piece, and this completes it.

Reviewed-by: Pavel Stehule <pavel.stehule@gmail.com>
Discussion: https://www.postgresql.org/message-id/flat/6e7aa4a1-be6a-1a75-b1f9-83a678e5184a@2ndquadrant.com
src/backend/commands/createas.c
src/backend/commands/explain.c
src/backend/commands/portalcmds.c
src/backend/commands/prepare.c
src/backend/tcop/utility.c
src/include/commands/createas.h
src/include/commands/explain.h
src/include/commands/portalcmds.h
src/include/commands/prepare.h