Skip site navigation (1) Skip section navigation (2)

Re: Review of last summer's PITR patch

From: Cott Lang <cott(at)internetstaff(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers-pitr(at)postgresql(dot)org
Subject: Re: Review of last summer's PITR patch
Date: 2004-02-13 01:25:35
Message-ID: 1076635535.4314.1.camel@blackbox (view raw or flat)
Thread:
Lists: pgsql-hackers-pitr
On Thu, 2004-02-12 at 18:14, Tom Lane wrote:
> Cott Lang <cott(at)internetstaff(dot)com> writes:
> > * The ability to force a WAL log switch to ensure all changes during the
> > backup are flushed to archived logs and copied.
> 
> Why does that require a log switch?  You can copy the active log file in
> any case.  (There was actually code to do that in J.R.'s patch, which I
> disregarded because I see no point in it ...)

Maybe it doesn't, I'm certainly no expert in PG internals. :)

It just seems like a Good Thing (TM) to ensure that any possible changes
to the data files during the backup are in the logs that are copied to
the archive destination and backed up as part of the hot backup.




In response to

pgsql-hackers-pitr by date

Next:From: Mark KirkwoodDate: 2004-02-13 04:29:28
Subject: Re: Review of last summer's PITR patch
Previous:From: Tom LaneDate: 2004-02-13 01:14:23
Subject: Re: Review of last summer's PITR patch

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group