Re: Read Uncommitted - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Read Uncommitted
Date
Msg-id 1211830340.4489.82.camel@ebony.site
Whole thread Raw
In response to Re: Read Uncommitted  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Read Uncommitted  ("Heikki Linnakangas" <heikki@enterprisedb.com>)
List pgsql-hackers
On Mon, 2008-05-26 at 13:25 -0400, Tom Lane wrote:
> Hannu Krosing <hannu@krosing.net> writes:
> > On Mon, 2008-05-26 at 16:55 +0200, Peter Eisentraut wrote:
> >> If the data in a table never changes, why would VACUUM or HOT need to touch 
> >> it?  The use case isn't clear to me.
> 
> > I guess the use-case is about a long read-write transaction doing
> > read-only access to an update-only table and thus blocking vacuum on
> > other tables.
> 
> ... in which case the proposed kluge would result in unstable,
> unpredictable answers, so there is still no plausible use-case.

Separate databases?

-- Simon Riggs           www.2ndQuadrant.comPostgreSQL Training, Services and Support



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Read Uncommitted
Next
From: Euler Taveira de Oliveira
Date:
Subject: Re: Help with new contrib