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/postgresq
Re: Martin Pitt 2012-12-19 <20121219095452.gd3...@piware.de>
> 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,
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 wa
Re: Martin Pitt 2012-12-17 <20121217070817.gb2...@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
severity 696138 wishlist
thanks
Martin Pitt dixit:
>>From IRC ping:
Thanks for following up on this.
>[19:18:02] for example, on my box, the script timeouted just beforee the db
>came up successfully
Actually, that was while doing a build in parallel, so it should
probably finish within 45s o
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?
[19:18:02] for example, on my box, the script timeouted just beforee the db
came up
6 matches
Mail list logo
