Comment 10 for bug 154012

Revision history for this message
Decibel (decibel) wrote : Re: [Bug 154012] Re: pg_ctlcluster uses stop immediate on it's own

Cool, thanks!

On Sun, Feb 03, 2008 at 11:49:33AM -0000, Martin Pitt wrote:
> Fixed in Hardy in this version:
>
> postgresql-common (82) unstable; urgency=low
>
> * debian/control: Fix 'commmon' typo. (Closes: #449532)
> * t/030_errors.t: Check that an /etc/postgresql/postgresql.conf leftover is
> not regarded as a cluster directory. This reproduces #450565.
> * PgCommon.pm, get_versions()/get_version_clusters(): Filter out '.' and
> '..' from readdir() output. (Closes: #450565)
> * pg_ctlcluster: Use "smart" mode shutdown by default, and add option
> -f/--force to use "fast" -> "immediate" -> kill -9 approach. (LP: #154012)
> * debian/init.d-functions: Use --force when stopping all clusters, since
> default smart mode can potentially block forever and thus fail to shut
> down a machine.
> * debian/README.Devel: Update for current bzr versions and hosting on
> code.launchpad.net.
> * Update Japanese debconf translations (Closes: #450902)
>
> -- Martin Pitt <email address hidden> Sun, 30 Dec 2007 22:27:08 +0100
>
>
> ** Changed in: postgresql-common (Ubuntu)
> Status: Triaged => Fix Released
>
> --
> pg_ctlcluster uses stop immediate on it's own
> https://bugs.launchpad.net/bugs/154012
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Decibel!, aka Jim C. Nasby, Database Architect <email address hidden>
Give your computer some brain candy! www.distributed.net Team #1828