aboutsummaryrefslogtreecommitdiff
path: root/contrib/btree_gist/btree_int4.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2009-12-02 04:38:35 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2009-12-02 04:38:35 +0000
commit3dfcf8cc15aeae3d30a0470b7d6bd5d4d462805d (patch)
treea34068e3ec194d1e2254fa40fe932ef910d93668 /contrib/btree_gist/btree_int4.c
parent925b32bba17179aee759f52791c50dea8cfb41b8 (diff)
downloadpostgresql-3dfcf8cc15aeae3d30a0470b7d6bd5d4d462805d.tar.gz
postgresql-3dfcf8cc15aeae3d30a0470b7d6bd5d4d462805d.zip
Instead of sending application_name as a SET command after the connection
is made, include it in the startup-packet options. This makes it work more like every other libpq connection option, in particular it now has the same response to RESET ALL as the rest. This also saves one network round trip for new applications using application_name. The cost is that if the server is pre-8.5, it'll reject the startup packet altogether, forcing us to retry the entire connection cycle. But on balance we shouldn't be optimizing that case in preference to the behavior with a new server, especially when doing so creates visible behavioral oddities. Per discussion.
Diffstat (limited to 'contrib/btree_gist/btree_int4.c')
0 files changed, 0 insertions, 0 deletions