| From: | "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM> |
|---|---|
| To: | "'Bruce Momjian'" <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | RE: Plans for solving the VACUUM problem |
| Date: | 2001-05-19 01:10:10 |
| Message-ID: | 3705826352029646A3E91C53F7189E3201662E@sectorbase2.sectorbase.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Vadim, can you remind me what UNDO is used for?
Ok, last reminder -:))
On transaction abort, read WAL records and undo (rollback)
changes made in storage. Would allow:
1. Reclaim space allocated by aborted transactions.
2. Implement SAVEPOINTs.
Just to remind -:) - in the event of error discovered by server
- duplicate key, deadlock, command mistyping, etc, - transaction
will be rolled back to the nearest implicit savepoint setted
just before query execution; - or transaction can be aborted by
ROLLBACK TO <savepoint_name> command to some explicit savepoint
setted by user. Transaction rolled back to savepoint may be continued.
3. Reuse transaction IDs on postmaster restart.
4. Split pg_log into small files with ability to remove old ones (which
do not hold statuses for any running transactions).
Vadim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-05-19 01:14:21 | Re: Problems with avg on interval data type |
| Previous Message | Peter Eisentraut | 2001-05-19 00:55:12 | Re: Re: Problems with avg on interval data type |