This has been saved for the 8.4 release:
http://momjian.postgresql.org/cgi-bin/pgpatches_hold
---
Simon Riggs wrote:
> On Sun, 2007-06-10 at 20:48 +0200, [EMAIL PROTECTED] wrote:
> > >
> > > > My questions was: why
How about adding to the general TODO in case someone finds time
before Simon?
On Jun 10, 2007, at 5:55 PM, Simon Riggs wrote:
On Sun, 2007-06-10 at 20:48 +0200, [EMAIL PROTECTED] wrote:
My questions was: why don't we start the archiving *BEFORE*
postmaster to
make room.
The archiver is
-hackers list
> Subject: Re: [HACKERS] little PITR annoyance
>
> On Sun, 2007-06-10 at 20:48 +0200, [EMAIL PROTECTED] wrote:
> > >
> > > > My questions was: why don't we start the archiving *BEFORE* postmaster
> > > > to
> > > > mak
On Sun, 2007-06-10 at 20:48 +0200, [EMAIL PROTECTED] wrote:
> >
> > > My questions was: why don't we start the archiving *BEFORE* postmaster to
> > > make room.
> >
> > The archiver is executed from the postmaster, so thats not possible.
> >
> I'm aware of that, my point is maybe the archiver doesn
Hi Simon,
Sorry for replying so late...
On Fri, 8 Jun 2007, Simon Riggs wrote:
> Date: Fri, 08 Jun 2007 20:16:35 +0100
> From: Simon Riggs <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Cc: pgsql-hackers list
> Subject: Re: [HACKERS] little PITR annoyance
>
> Hi Olivier
Hi Olivier,
On Fri, 2007-06-08 at 11:41 +0200, [EMAIL PROTECTED] wrote:
> 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.
The archiver is executed from
Hi Simon,
On Thu, 7 Jun 2007, Simon Riggs wrote:
> Date: Thu, 07 Jun 2007 23:10:06 +0100
> From: Simon Riggs <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Cc: pgsql-hackers list
> Subject: Re: [HACKERS] little PITR annoyance
>
> On Thu, 2007-06-07 at 17:01 +02
On Thu, 2007-06-07 at 17:01 +0200, [EMAIL PROTECTED] 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 dow
Hi all,
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
