Received: from maia.hub.org (maia-3.hub.org [200.46.204.243])
	by mail.postgresql.org (Postfix) with ESMTP id 1C1BD1337B69
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Mon, 25 Apr 2011 16:57:25 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia,
	port 10024)
	with ESMTP id 83343-05; Mon, 25 Apr 2011 19:57:17 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from mail-yw0-f46.google.com (mail-yw0-f46.google.com
	[209.85.213.46])
	by mail.postgresql.org (Postfix) with ESMTP id 05CB8133740B;
	Mon, 25 Apr 2011 16:57:16 -0300 (ADT)
Received: by ywj3 with SMTP id 3so755401ywj.19
	for <multiple recipients>; Mon, 25 Apr 2011 12:57:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:cc:content-type;
	bh=E6/5jV1B93QLzHik1h8R9LKcusH93FHK9qpZSAfCXbA=;
	b=d4AT0SAx6MUlUiMS/1xE8iyAxs1L9TzB8onPR5ro7UBm2tae09WeVN20+xeZitaZrn
	rIYosTMw+G8r/h8GteRc1L0bacbHf0EBZPg3GclDLBz6zuEsgRIN2vimg2cqPBZy0mUV
	LgmYklu9fh2koxEEPG2wtC5r0yfsS2NtKD5UI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	b=AL8WvlEFuUCoaGYh16/MoOt82AulFqoygbu46PW6EZNVL6vLQq1ulENdfF5gPSRy9c
	IGYymjYyPto9WmeEqMyEQ15fHBacimbGnzdMm5n4/XvAzLyVz6f0MHBH47x6vvFrPcgZ
	JMj6PXLhYERQjlXBj1PHpD5MnRgDCjQLnICTU=
MIME-Version: 1.0
Received: by 10.236.195.3 with SMTP id o3mr4574313yhn.133.1303761437514; Mon,
	25 Apr 2011 12:57:17 -0700 (PDT)
Received: by 10.236.105.212 with HTTP; Mon, 25 Apr 2011 12:57:17 -0700 (PDT)
In-Reply-To: <D100DC2FEE9E48788D640D6E7E110D21@DEVELOP1>
References: <00C88DF265FC483EBE2322C834A76698@DEVELOP1>
	<4DA42B42020000250003C6F8@gw.wicourts.gov>
	<3670D8885C9549A393E47A0C1582B07A@DEVELOP1>
	<4DA45EA2020000250003C711@gw.wicourts.gov>
	<6A526FFBDB9D4EE2947C4E5E282530E3@DEVELOP1>
	<BANLkTimwwzsxhq36T4k7jNUexPEiyeVz_w@mail.gmail.com>
	<D100DC2FEE9E48788D640D6E7E110D21@DEVELOP1>
Date: Mon, 25 Apr 2011 15:57:17 -0400
Message-ID: <BANLkTi=QOf2v3fZhTPqq3TLR+-HeQFgJnA@mail.gmail.com>
Subject: Re: [BUGS] [JDBC] Missing documentation for error code: 80S01
From: Robert Haas <robertmhaas@gmail.com>
To: Donald Fraser <postgres@kiwi-fraser.net>
Cc: "[BUGS]" <pgsql-bugs@postgresql.org>,
	"[ADMIN]" <pgsql-admin@postgresql.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-1.898 tagged_above=-10 required=5
	tests=BAYES_00=-1.9, FREEMAIL_FROM=0.001, RFC_ABUSE_POST=0.001
X-Spam-Level: 
X-Archive-Number: 201104/225
X-Sequence-Number: 37406

On Wed, Apr 13, 2011 at 6:52 AM, Donald Fraser <postgres@kiwi-fraser.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