Hi Simon,
On Thu, 7 Jun 2007, Simon Riggs wrote:
> Date: Thu, 07 Jun 2007 23:10:06 +0100
> From: Simon Riggs <simon@2ndquadrant.com>
> To: ohp@pyrenet.fr
> Cc: pgsql-hackers list <pgsql-hackers@postgresql.org>
> Subject: Re: [HACKERS] little PITR annoyance
>
> On Thu, 2007-06-07 at 17:01 +0200, ohp@pyrenet.fr wrote:
>
> > I've benn biten twice by this one:
> > I enabled archiving on both my pgsql servers.
> > the archive command was a simple gzip on an nfs mounted dir.
> > Now the nfs server crashed.
> > Both wal space filled up until postgresql shuts itself down because of no
> > more space for WAL.
> > That perfectly normal and expected.
> >
> > What I did'nt expect and don't understand is that postgresql refused to
> > start up after the nfs server was up and running until I added some more
> > space on the WAL fs although if it had started archiving ,
> > space would have been there .
> >
> > I wonder if archiving could start before postgresql at least to make a
> > little room for database engine to really start.
>
> gzip write a new file and then deletes the old, doesn't it? So it must
> require space on the xlog drive.
>
> Does it still fail if you avoid using gzip and just use scp?
The problem is not with gzip or scp, it is that postmaster refuses to
start because wal FS is full.
My questions was: why don't we start the archiving *BEFORE* postmaster to
make room.
Another related question would be: What if postmaster instead of shutting
down in that case, refused connection until archiving is back?
Many thanks
>
>
--
Olivier PRENANT Tel: +33-5-61-50-97-00 (Work)
15, Chemin des Monges +33-5-61-50-97-01 (Fax)
31190 AUTERIVE +33-6-07-63-80-64 (GSM)
FRANCE Email: ohp@pyrenet.fr
------------------------------------------------------------------------------
Make your life a dream, make your dream a reality. (St Exupery)
