]> granicus.if.org Git - postgresql/commit
After closing frontend socket, set MyProcPort->sock = -1 to ensure that
authorTom Lane <tgl@sss.pgh.pa.us>
Fri, 26 May 2000 01:26:19 +0000 (01:26 +0000)
committerTom Lane <tgl@sss.pgh.pa.us>
Fri, 26 May 2000 01:26:19 +0000 (01:26 +0000)
commit2af53f3762513e397177d9b13dcfdbba7effc7a0
tree3fc0a0b43e627d237b8b58e34fb765625e21ecf4
parent39725e56e8a1271b2ba01c25aa0babf729f1f372
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.
src/backend/libpq/pqcomm.c