Skip site navigation (1) Skip section navigation (2)

Re: [BUGS] [JDBC] Missing documentation for error code: 80S01

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 (view raw or flat)
Thread:
Lists: pgsql-adminpgsql-bugspgsql-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

In response to

pgsql-admin by date

Next:From: Scott RibeDate: 2011-04-25 20:14:14
Subject: validating database integrity
Previous:From: hirenladDate: 2011-04-25 12:55:31
Subject: postgresql 8.4.msi

pgsql-bugs by date

Next:From: Tom LaneDate: 2011-04-25 20:23:17
Subject: Re: BUG #5993: pg_size_pretty overflow
Previous:From: Robert HaasDate: 2011-04-25 17:18:36
Subject: Re: BUG #5988: CTINE duplicates constraints

pgsql-jdbc by date

Next:From: Kevin GrittnerDate: 2011-04-25 21:06:45
Subject: Re: Unnessecary use of new Integer(n) in AbstractJdbc2ResultSet
Previous:From: LewDate: 2011-04-25 16:44:32
Subject: Re: Unnessecary use of new Integer(n) in AbstractJdbc2ResultSet

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group