From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Donald Fraser <postgres(at)kiwi-fraser(dot)net> |
Cc: | "[BUGS]" <pgsql-bugs(at)postgresql(dot)org>, "[ADMIN]" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: [BUGS] [JDBC] Missing documentation for error code: 80S01 |
Date: | 2011-04-25 19:57:17 |
Message-ID: | BANLkTi=QOf2v3fZhTPqq3TLR+-HeQFgJnA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-bugs pgsql-jdbc |
On Wed, Apr 13, 2011 at 6:52 AM, Donald Fraser <postgres(at)kiwi-fraser(dot)net> wrote:
>> 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.
A smart shutdown waits for clients to exit on their own. A fast or
immediate shutdown kills them immediately, even mid-query.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Ribe | 2011-04-25 20:14:14 | validating database integrity |
Previous Message | hirenlad | 2011-04-25 12:55:31 | postgresql 8.4.msi |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-04-25 20:23:17 | Re: BUG #5993: pg_size_pretty overflow |
Previous Message | Robert Haas | 2011-04-25 17:18:36 | Re: BUG #5988: CTINE duplicates constraints |
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2011-04-25 21:06:45 | Re: Unnessecary use of new Integer(n) in AbstractJdbc2ResultSet |
Previous Message | Lew | 2011-04-25 16:44:32 | Re: Unnessecary use of new Integer(n) in AbstractJdbc2ResultSet |