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

Re: Shutdown fails with both 'fast' and 'immediate'

From: David Schnur <dnschnur(at)gmail(dot)com>
To: pgsql-admin(at)postgresql(dot)org
Subject: Re: Shutdown fails with both 'fast' and 'immediate'
Date: 2010-05-12 17:03:57
Message-ID: AANLkTilzcY_VGBiYdTJ2bomtECxJxipSyW4AcpLMsO76@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-admin
@Julio Leyva: The table does get vacuumed at the end of the maintenance
tasks; in this case it's not making it that far, of course.

@Scott Marlowe: Truncate isn't an option here, unfortunately.

I'm less concerned with the particular query than with the general question
of when a shutdown could hang like this.  I expected this to be possible
when using -m fast, but my understanding was that -m immediate really forced
termination.

I'm setting up a test on the user's machine where it will try immediate
first, rather than fast.

David

In response to

Responses

pgsql-admin by date

Next:From: Tom LaneDate: 2010-05-12 17:16:13
Subject: Re: Shutdown fails with both 'fast' and 'immediate'
Previous:From: Robert HaasDate: 2010-05-12 16:24:22
Subject: Re: List traffic

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