Re: Vacuum dead tuples that are "between"

Поиск
Список
Период
Сортировка
Искать
От
Kevin Grittner
Тема
Re: Vacuum dead tuples that are "between"
Дата
Msg-id
440575F5.EE98.0025.0@wicourts.gov
Ответ на
Список
Дерево обсуждения
Vacuum dead tuples that are "between" transactions Paul Tillotson <spam1011@adelphia.net>
Re: Vacuum dead tuples that are "between" transactions Tom Lane <tgl@sss.pgh.pa.us>
Re: Vacuum dead tuples that are "between" transactions Simon Riggs <simon@2ndquadrant.com>
Re: Vacuum dead tuples that are "between" transactions "Jim C. Nasby" <jnasby@pervasive.com>
Re: Vacuum dead tuples that are "between" "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: Vacuum dead tuples that are "between" transactions Simon Riggs <simon@2ndquadrant.com>
Wisconsin Court Systems software "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: Vacuum dead tuples that are "between" transactions "Jim C. Nasby" <jnasby@pervasive.com>
>>> On Tue, Feb 28, 2006 at  7:22 am, in message
<1141132955.27729.119.camel@localhost.localdomain>, Simon Riggs
 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



В списке pgsql-hackers по дате отправления
От: Tom Lane
Дата:
От: Robert Treat
Дата:
FAQ