From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Decibel! <decibel(at)decibel(dot)org> |
Cc: | Gregory Stark <stark(at)enterprisedb(dot)com>, Steve Crawford <scrawford(at)pinpointresearch(dot)com>, "Joey K(dot)" <pguser(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Seeking datacenter PITR backup suggestions |
Date: | 2007-08-29 01:54:23 |
Message-ID: | 19317.1188352463@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Decibel! <decibel(at)decibel(dot)org> writes:
> On Tue, Aug 28, 2007 at 08:31:10PM +0100, Gregory Stark wrote:
>> Postgres tries to reuse WAL files. Once the archive_command completes it
>> believes it is safe to reuse the old file without deleting it. That will do
>> nasty things if you've used ln as your archive command.
> I thought that was specifically disabled when PITR was enabled? Or do we
> just do a rename rather than an unlink ond creating a new file?
No. The only difference is we don't recycle the file until the
archive_command says it's done with it.
The archive_command must actually physically copy the data someplace
else, and must not return success until it's sure the copy is good.
Perhaps the docs are not sufficiently clear on the point?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Decibel! | 2007-08-29 02:04:26 | Re: Seeking datacenter PITR backup suggestions |
Previous Message | Alvaro Herrera | 2007-08-29 01:47:00 | Re: Out of Memory - 8.2.4 |