| From: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> |
|---|---|
| To: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | AW: Re: Backup and Recovery |
| Date: | 2001-07-06 08:22:24 |
| Message-ID: | 11C1E6749A55D411A9670001FA687963368368@sdexcsrv1.f000.d0188.sd.spardat.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > In other words, we keep the page images and row records in one file so
> > we can do one fsync, but once we have written the page, we don't want to
> > store them for later point-in-time recovery.
>
> What we'd want to do is strip the page images from the version of the
> logs that's archived for recovery purposes. Ideally the archiving
> process would also discard records from aborted transactions, but I'm
> not sure how hard that'd be to do.
Unless we have UNDO we also need to roll forward the physical changes of
aborted transactions, or later redo records will "sit on a wrong physical image".
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Víctor Romero | 2001-07-06 08:52:33 | Re: Pg on SMP half-powered |
| Previous Message | Matthew Hagerty | 2001-07-06 05:23:06 | Proper use of select() parameter nfds? |