| From: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> |
|---|---|
| To: | "'Philip Warner'" <pjw(at)rhyme(dot)com(dot)au>, "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM>, "'Bruce Momjian'" <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | The Hermit Hacker <scrappy(at)hub(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | AW: AW: Plans for solving the VACUUM problem |
| Date: | 2001-05-23 11:08:28 |
| Message-ID: | 11C1E6749A55D411A9670001FA6879633682F2@sdexcsrv1.f000.d0188.sd.spardat.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> - A simple typo in psql can currently cause a forced rollback of the entire
> TX. UNDO should avoid this.
Yes, I forgot to mention this very big advantage, but undo is not the only possible way
to implement savepoints. Solutions using CommandCounter have been discussed.
Although the pg_log mechanism would become more complex, a background
"vacuum-like" process could put highest priority on removing such rolled back parts
of transactions.
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-05-23 13:05:47 | Re: More pgindent follies |
| Previous Message | Stephen Deasey | 2001-05-23 10:48:58 | select ... for update and inheritence |