| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Hannu Krosing <hannu(at)tm(dot)ee> |
| Cc: | Barry Lind <barry(at)xythos(dot)com>, Patrick Macdonald <patrickm(at)redhat(dot)com>, Zeugswetter Andreas SB SD <ZeugswetterA(at)spardat(dot)at>, "J(dot) R(dot) Nield" <jrnield(at)usol(dot)com>, PostgreSQL Hacker <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Issues Outstanding for Point In Time Recovery (PITR) |
| Date: | 2002-07-09 15:26:55 |
| Message-ID: | 4626.1026228415@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hannu Krosing <hannu(at)tm(dot)ee> writes:
> 1) record the lowest uncommitted transaction number (LUTN) , this may
> have problems with wraparound, but I guess they are solvable. Disllow
> VACUUM. Do a CHECKPOINT ('alter database begin backup')
> 3) make a file-level (.tar) backup of data directory.
> 4) Allow VACUUM. ('alter database end backup')
Transactions don't necessarily commit in sequence number order, so the
concept of LUTN seems meaningless.
Why is it necessary (or even good) to disallow VACUUM? I really dislike
a design that allows the DBA to cripple the database by forgetting the
last step in a (long) process.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Lockhart | 2002-07-09 15:27:23 | Re: Units for storage of internal time zone offsets |
| Previous Message | Lamar Owen | 2002-07-09 15:19:09 | Re: (A) native Windows port |