From: | "Donald Fraser" <postgres(at)kiwi-fraser(dot)net> |
---|---|
To: | "[BUGS]" <pgsql-bugs(at)postgresql(dot)org>, "[ADMIN]" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: [JDBC] Missing documentation for error code: 80S01 |
Date: | 2011-04-13 10:52:13 |
Message-ID: | D100DC2FEE9E48788D640D6E7E110D21@DEVELOP1 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-bugs pgsql-jdbc |
From: "Oliver Jowett" <oliver(at)opencloud(dot)com>
> If the server is shut down mid-query, doesn't the backend complete the
> current query cycle before closing the connection?
> i.e. we'd see ErrorResponse, ReadyForQuery, and return control to the
> app before seeing EOF anyway?
> The protocol spec is a bit vague there.
From an observation perspective only: It would seem that in the case where
the server is shut down gracefully yes, however in the case where the server
has either crashed or the connection terminated un-gracefully via software
control (for example a C funcion: elog(FATAL, "Terminating connection...");)
then no.
Donald
From | Date | Subject | |
---|---|---|---|
Next Message | Vibhor Kumar | 2011-04-13 11:58:48 | Re: unsupported header version error |
Previous Message | Oliver Jowett | 2011-04-13 10:30:17 | Re: [JDBC] Missing documentation for error code: 80S01 |
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2011-04-13 11:18:30 | Re: 9.1 doesn't start when died mid-backup |
Previous Message | Oliver Jowett | 2011-04-13 10:30:17 | Re: [JDBC] Missing documentation for error code: 80S01 |
From | Date | Subject | |
---|---|---|---|
Next Message | Kasprzyk Maciej-FHC368 | 2011-04-14 11:10:30 | feature request: make support for java.sql.Types.DISTINCT optional |
Previous Message | Oliver Jowett | 2011-04-13 10:30:17 | Re: [JDBC] Missing documentation for error code: 80S01 |