| From: | "Vadim Mikheev" <vmikheev(at)sectorbase(dot)com> |
|---|---|
| To: | "Zeugswetter Andreas SB" <ZeugswetterA(at)wien(dot)spardat(dot)at>, "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: RE: xlog loose ends, continued |
| Date: | 2001-03-13 16:02:00 |
| Message-ID: | 008601c0abd6$f0a57460$4c79583f@sectorbase.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > Anyway I like idea of StartUpID in page headers - this will help
>
> Can you please describe StartUpID for me ?
> Ideal would be a stamp that has the last (smallest open) XID, or something else
> that has more or less timestamp characteristics (without the actual need of wallclock)
> in regard to the WAL.
StartUpID counts database startups and so has timestamp characteristics.
Actually, idea is to use SUI in future to allow reusing XIDs after startup: seeing
old SUI in data pages we'll know that all transaction on this page was committed
"long ago" (ie visible from MVCC POV). This requires UNDO, of course.
> This could then also be used to scan all pages for modification since
> last backup, to make incremental backups possible. (note, that incremental
> backup is not WAL backup)
We can scan log itself to get all pages modified since last backup or whatever
point we want - thanks to your idea about data pages backup.
Vadim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2001-03-13 16:04:25 | Re: Performance monitor |
| Previous Message | Tom Lane | 2001-03-13 16:01:07 | Re: Performance monitor |