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

2013-09-01 Thread Thorsten Glaser
Martin Pitt dixit:

Christoph Berg [2012-12-19 10:40 +0100]:
 We could probably wait for the startup, but then exit 0 with the
 message cluster is still starting up.

I like that idea. It should avoid postinst failures on slow
architectures, but in the normal case a /etc/init.d/postgresql
restart should still wait until your cluster is ready to be used.

I think this does not work. One use case here is a buildd that
tries to build something that is a PostgreSQL client, which then
runs a DB server during its testsuite.

I really think that the initscript needs to wait here, possibly
pretty long (DB recovery was already mentioned) – after all,
pgsql comes from BSD land “better slow than unsafe”.

bye,
//mirabilos
-- 
21:27⎜[Natureshadow] BÄH! Wer hatn das Bier neben den Notebooklüfter
 ⎜gestellt ... Das ist ja warm!
21:27⎜Natureshadow lol 21:27⎜Natureshadow du?
21:27⎜[Natureshadow] vermutlich ...   -- Kev^WNatureshadow allein zu Haus


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



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

2012-12-19 Thread Martin Pitt
Christoph Berg [2012-12-19 10:40 +0100]:
 We could probably wait for the startup, but then exit 0 with the
 message cluster is still starting up.

I like that idea. It should avoid postinst failures on slow
architectures, but in the normal case a /etc/init.d/postgresql
restart should still wait until your cluster is ready to be used.

Martin
-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)


signature.asc
Description: Digital signature