Re: How is statement level read consistency implemented?

From: "Roberts, Jon" <Jon(dot)Roberts(at)asurion(dot)com>
To: "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>
Cc: "Thomas Kellerer" <spam_eater(at)gmx(dot)net>, <pgsql-general(at)postgresql(dot)org>
Subject: Re: How is statement level read consistency implemented?
Date: 2008-04-22 13:20:18
Message-ID: 1A6E6D554222284AB25ABE3229A92762E9A1F9@nrtexcus702.int.asurion.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> > Back to PostgreSQL, when a vacuum is issued, the old deleted rows
are
> > removed. This can be done with the autovacuum feature or manually.
> >
> > -Does vacuum make sure there are no long running queries referencing
the
> > deleted rows before it attempts to remove the old rows?
>
> It does.
>
> > -With autovacuum, does it skip these rows still being referenced in
a
> > transaction or does it wait?
>
> It skips them, the idea being that a future vacuum will remove them.
>

Awesome. In a large data warehouse, the snapshot too old error is very
annoying and I'm glad PostgreSQL is superior to Oracle in this regard.
:)

Jon

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Kerri Reno 2008-04-22 13:26:58 Re: FW: Re: create temp in function
Previous Message Pavel Stehule 2008-04-22 13:10:57 Re: FW: Re: create temp in function