From: | Jean Arnaud <Jean(dot)Arnaud(at)inrialpes(dot)fr> |
---|---|
To: | Rajesh Kumar Mallah <mallah(dot)rajesh(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Restart time |
Date: | 2006-12-06 08:44:16 |
Message-ID: | 457682E0.9000206@inrialpes.fr |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Rajesh Kumar Mallah a écrit :
>
>
> On 12/5/06, *Tom Lane* <tgl(at)sss(dot)pgh(dot)pa(dot)us <mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us>>
> wrote:
>
> Jean Arnaud <Jean(dot)Arnaud(at)inrialpes(dot)fr
> <mailto:Jean(dot)Arnaud(at)inrialpes(dot)fr>> writes:
> > Is there a relation between database size and PostGreSQL restart
> duration ?
>
> No.
>
> > Does anyone now the behavior of restart time ?
>
> It depends on how many updates were applied since the last checkpoint
> before the crash.
>
> If you're talking about startup of a cleanly-shut-down database, it
> should be pretty much constant time.
>
>
> Dear Sir,
>
> Startup time of a clean shutdown database is constant. But we still
> face problem when it comes to shutting down. PostgreSQL waits
> for clients to finish gracefully. till date i have never been able to
> shutdown
> quickly (web application scenerio) and i tend to do pg_ctl -m
> immediate stop
> mostly.
>
>
> regards, tom lane
>
Hi
Thanks everybody for answers !
To be sure SGBD will stop before a certain time, I use function that is
a combination of pg_ctl -m fast to stop most of process cleanly, and
after few seconds, I send pg_ctl -m immediate to be shut down immediatly
the system if not already stoped. This works pretty well in practice and
offers a good compromise between clean and fast shutdown.
Cheers
--
--- Jean Arnaud
--- Projet SARDES
--- INRIA Rhône-Alpes
From | Date | Subject | |
---|---|---|---|
Next Message | Sven Geisler | 2006-12-06 09:09:25 | Re: Hardware advice |
Previous Message | Markus Schiltknecht | 2006-12-06 07:11:44 | Re: Locking in PostgreSQL? |