Wed Nov 3 15:07:13 PST 2004
- Previous message: [Slony1-general] Slonik 'EXIT' command not closing database connection properly
- Next message: [Slony1-general] Slonik 'EXIT' command not closing database connection properly
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 11/2/2004 11:52 PM, Justin Clift wrote: > Hi all, > > Trying out the Slonik EXIT command now to indicate various successes and > failures. > > PostgreSQL is always giving this error message when Slonik uses the EXIT > command instead of just finishing the input script naturally: > > ******* > > LOG: unexpected EOF on client connection Right ... the exit command simply does exit(2), which causes the kernel to close all sockets the hard way and the backend misses the X message. Jan > > ******* > > Is there any chance the EXIT command is finishing things without closing > down the PG connection properly? > > Regards and best wishes, > > Justin Clift > > _______________________________________________ > Slony1-general mailing list > Slony1-general at gborg.postgresql.org > http://gborg.postgresql.org/mailman/listinfo/slony1-general -- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #================================================== JanWieck at Yahoo.com #
- Previous message: [Slony1-general] Slonik 'EXIT' command not closing database connection properly
- Next message: [Slony1-general] Slonik 'EXIT' command not closing database connection properly
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list