From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
---|---|
To: | "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Paul Tillotson" <spam1011(at)adelphia(dot)net>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Vacuum dead tuples that are "between" |
Date: | 2006-03-01 16:22:45 |
Message-ID: | 440575F5.EE98.0025.0@wicourts.gov |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>>> On Tue, Feb 28, 2006 at 7:22 am, in message
<1141132955(dot)27729(dot)119(dot)camel(at)localhost(dot)localdomain>, Simon Riggs
<simon(at)2ndquadrant(dot)com> wrote:
>
> OTOH a few hackers discussed this recently and found that nobody
used
> serializable transactions (ST) except during pg_dump.
I've not been able to keep up with all messages on these lists, and I
missed that discussion.
We use serializable transactions heavily; our whole middle tier
architecture depends on having that transaction isolation level for all
requests which modify data. (You probably don't want to hear the
details.) It would be OK (although a little disappointing) if VACUUM
enhancements weren't as beneficial to us as a result; it would render
PostgreSQL entirely unusable for us if the integrity of serializable
transactions was broken unless we added some other, non-standard steps
to run them.
We only use pg_dump for version upgrades and other special cases. PITR
is our main backup technique.
-Kevin
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2006-03-01 16:26:21 | Re: Initdb on Windows 2003 |
Previous Message | Peter Eisentraut | 2006-03-01 16:16:16 | Re: Automatic free space map filling |