From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Zeugswetter Andreas SB SD <ZeugswetterA(at)spardat(dot)at> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Marc Munro <marc(at)bloodnok(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: point in time recovery and moving datafiles online |
Date: | 2002-02-22 18:30:07 |
Message-ID: | 200202221830.g1MIU7a02183@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Zeugswetter Andreas SB SD wrote:
> > > Yes. But I think you might have to avoid "vacuum full" during data file backup.
> >
> > Why? If vacuum is unsafe in this scenario, wouldn't it also be unsafe
> > in event of a system crash?
>
> I was not sure we are 100% crash safe during "vacuum full".
> But yes, now recalling your last remark on a crash during vacuum full
> I guess we should be.
>
> > I do believe that vacuum should (but presently does not) emit a WAL
> > record showing its truncation of the file, so that the equivalent
> > truncation can be repeated during replay.
>
> > However, this is needed in any case.
>
> I see, but it has only the effect of not freeing the space to the OS,
> so it is not really a bug ? Next vacuum will do it anyway.
One idea is that replication can give is point-in-time recovery. A
recovery is nothing more than a replication slave taking the last full
backup and reading the replication traffic to get itself up to date.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-02-22 18:50:47 | Going through email |
Previous Message | Sean Chittenden | 2002-02-22 18:25:04 | Re: Replication direction |