aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2000-05-26 01:26:19 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2000-05-26 01:26:19 +0000
commit2af53f3762513e397177d9b13dcfdbba7effc7a0 (patch)
tree3fc0a0b43e627d237b8b58e34fb765625e21ecf4 /src/backend/access/gist
parent39725e56e8a1271b2ba01c25aa0babf729f1f372 (diff)
downloadpostgresql-2af53f3762513e397177d9b13dcfdbba7effc7a0.tar.gz
postgresql-2af53f3762513e397177d9b13dcfdbba7effc7a0.zip
After closing frontend socket, set MyProcPort->sock = -1 to ensure that
subsequent I/O attempts fail cleanly. I'm speculating about failure scenarios in which we do pq_close, then something in a proc_exit routine opens a file (re-using that kernel FD number), then something else fails and tries to write an elog message to the frontend ... message ends up in opened file, oops. No known examples of this but it seems like a potential hole.
Diffstat (limited to 'src/backend/access/gist')
0 files changed, 0 insertions, 0 deletions