[Pkg-postgresql-public] Bug#696138: Increase pg_ctlcluster on slow architectures

Christoph Berg myon at debian.org
Wed Dec 19 09:40:57 UTC 2012

Re: Martin Pitt 2012-12-17 <20121217070817.GB2975 at piware.de>
> Package: postgresql-common
> Version: 129
> >From IRC ping:
> [19:17:48] hi, while you're working on postgresql-common: is it possible for it to wait more than one minute on slow arches such as m68k, avr32, sh4, etc?
> This needs some thinking as I don't quite like a complex arch →
> timeout lookup table, but more than a minute is quite excessive on
> architectures which are realistically being used as a database server.

Do we need to wait for a successful connect at all? If the cluster
happens to be recovering, that could take an arbitrary amount of time.
Wouldn't waiting for the pid file be enough?

We could probably wait for the startup, but then exit 0 with the
message "cluster is still starting up".

cb at df7cb.de | http://www.df7cb.de/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-postgresql-public/attachments/20121219/9ac29a86/attachment.pgp>

More information about the Pkg-postgresql-public mailing list