DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:date:message-id:subject:from:to:content-type;
	b=UiJmKjqQRpncYy7r+LGLwUk51kkDvynPUWHAz5782Cx5env49xQeb31njwVJE+FiVy
	tMtVCdG9JUoXWfe87E+lQeZki4ef81ruuIsQ0EVko/1ZoDHJ7XByglRCtAYS0qxLg0Sh
	6v7X4KmZUYdatQhsybzgFsvm6Iriv43cNWJGk=
MIME-Version: 1.0
Date: Wed, 12 May 2010 10:22:14 -0400
Message-ID: <AANLkTindCeLyRmRbgV4ICxEBGRLwyBbm5yO2oLBHUnSc@mail.gmail.com>
Subject: Shutdown fails with both 'fast' and 'immediate'
From: David Schnur <dnschnur@gmail.com>
To: pgsql-admin@postgresql.org
Content-Type: multipart/alternative; boundary=0016364267236134d60486665e22

--0016364267236134d60486665e22
Content-Type: text/plain; charset=ISO-8859-1

I develop an app that uses a back-end Postgres database, currently 8.3.9.
 The database is started when the app starts up, and stopped when it shuts
down.  Shutdown uses pg_ctl with -m fast, and waits two minutes for the
process to complete.  If it doesn't, it tries -m immediate, and waits two
more minutes before logging an error and giving up.

One user, on OSX 10.5.8, has a script that stops the app each morning, to
upgrade to the newest build.  In his case, both the fast and immediate
shutdowns time out, and Postgres continues running for at least 2-4 hours.
 At that point he brings up the terminal to kill all the back-ends manually,
so we haven't seen it finish shutting down on its own yet.  It is in fact
shutting down, because all queries fail with the 'database system is
shutting down' error.

The query running during this time is a DELETE that runs as part of the
application's daily maintenance.  The size of the DELETE varies, and in his
case happened to be unusually large one day, which is apparently what
triggered the problem.  Since the DELETE never gets a chance to finish, the
problem recurs every morning.

I'll obviously need to deal with that query, but I'm concerned that Postgres
is unable to interrupt it.  Why might this be happening?  Thanks,

David

--0016364267236134d60486665e22
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I develop an app that uses a back-end Postgres database, currently 8.3.9. =
=A0The database is started when the app starts up, and stopped when it shut=
s down. =A0Shutdown uses pg_ctl with -m fast, and waits two minutes for the=
 process to complete. =A0If it doesn&#39;t, it tries -m immediate, and wait=
s two more minutes before logging an error and giving up.<div>

<br></div><div>One user, on OSX 10.5.8, has a script that stops the app eac=
h morning, to upgrade to the newest build. =A0In his case, both the fast an=
d immediate shutdowns time out, and Postgres continues running for at least=
 2-4 hours. =A0At that point he brings up the terminal to kill all the back=
-ends manually, so we haven&#39;t seen it finish shutting down on its own y=
et. =A0It is in fact shutting down, because all queries fail with the &#39;=
database system is shutting down&#39; error.</div>

<div><br></div><div>The query running during this time is a DELETE that run=
s as part of the application&#39;s daily maintenance. =A0The size of the DE=
LETE varies, and in his case happened to be unusually large one day, which =
is apparently what triggered the problem. =A0Since the DELETE never gets a =
chance to finish, the problem recurs every morning.</div>

<div><br></div><div>I&#39;ll obviously need to deal with that query, but I&=
#39;m concerned that Postgres is unable to interrupt it. =A0Why might this =
be happening? =A0Thanks,</div>
<div><br></div><div>David</div>

--0016364267236134d60486665e22--