aboutsummaryrefslogtreecommitdiff
path: root/src/backend/parser/parse_expr.c
diff options
context:
space:
mode:
authorRobert Haas <rhaas@postgresql.org>2017-01-24 16:53:56 -0500
committerRobert Haas <rhaas@postgresql.org>2017-01-24 16:53:56 -0500
commita84069d9350400c860d5e932b50dfd337aa407b0 (patch)
treeac278978c902539d065211f2fb47c4a04d4b40f3 /src/backend/parser/parse_expr.c
parent7b4ac19982a77a1a2a6f096c4a11ee7325a14d2c (diff)
downloadpostgresql-a84069d9350400c860d5e932b50dfd337aa407b0.tar.gz
postgresql-a84069d9350400c860d5e932b50dfd337aa407b0.zip
Add a new DestReceiver for printing tuples without catalog access.
If you create a DestReciver of type DestRemote and try to use it from a replication connection that is not bound to a specific daabase, or any other hypothetical type of backend that is not bound to a specific database, it will fail because it doesn't have a pg_proc catalog to look up properties of the types being printed. In general, that's an unavoidable problem, but we can hardwire the properties of a few builtin types in order to support utility commands. This new DestReceiver of type DestRemoteSimple does just that. Patch by me, reviewed by Michael Paquier. Discussion: http://postgr.es/m/CA+TgmobNo4qz06wHEmy9DszAre3dYx-WNhHSCbU9SAwf+9Ft6g@mail.gmail.com
Diffstat (limited to 'src/backend/parser/parse_expr.c')
0 files changed, 0 insertions, 0 deletions