aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistbuild.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2012-09-07 16:02:23 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2012-09-07 16:02:23 -0400
commit210eb9b743c0645df05e5c8be4490ba4f09fc871 (patch)
tree8bd3c4d225a794eada3f8537f221b50fc6cafa11 /src/backend/access/gist/gistbuild.c
parentdda589c96b89320446933108ca946e7e6b8eb9d2 (diff)
downloadpostgresql-210eb9b743c0645df05e5c8be4490ba4f09fc871.tar.gz
postgresql-210eb9b743c0645df05e5c8be4490ba4f09fc871.zip
Centralize libpq's low-level code for dropping a connection.
Create an internal function pqDropConnection that does the physical socket close and cleans up closely-associated state. This removes a bunch of ad hoc, not always consistent closure code. The ulterior motive is to have a single place to wait for a spawned child backend to exit, but this seems like good cleanup even if that never happens. I went back and forth on whether to include "conn->status = CONNECTION_BAD" in pqDropConnection's actions, but for the moment decided not to. Only a minority of the call sites actually want that, and in any case it's arguable that conn->status is slightly higher-level state, and thus not part of this function's purview.
Diffstat (limited to 'src/backend/access/gist/gistbuild.c')
0 files changed, 0 insertions, 0 deletions