Our current RESET CONNECTION TODO item is:
* Add RESET CONNECTION command to reset all session state This would include resetting of all variables (RESET ALL),
droppingof temporary tables, removing any NOTIFYs, cursors, open transactions, prepared queries, currval()s, etc.
Thiscould be used for connection pooling. We could also change RESET ALL to have this functionality. The difficult
ofthis features is allowing RESET ALL to not affect changes made by the interface driver for its internal use. One
idea is for this to be a protocol-only feature. Another approach is to notify the protocol when a RESET CONNECTION
commandis used.
I know we have GUC variables that are passed automatically to the
client. I assume varaible changes are also automatically sent to the
client.
What if we create a 'reset_connection' guc that is initially false, and
is set to 'true' when someone resets a connection. Then, when it
happens, the client finds out, reconfigures whatever it needs, then sets
the value back to 'false'.
-- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610)
359-1001+ If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square,
Pennsylvania19073
