Re: Idea for getting rid of VACUUM FREEZE on cold pages - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Idea for getting rid of VACUUM FREEZE on cold pages
Date
Msg-id AANLkTinZ0m7iS2bvFQlxIWXWf8LSMRML06n86Y2_Ax3E@mail.gmail.com
Whole thread Raw
In response to Re: Idea for getting rid of VACUUM FREEZE on cold pages  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Responses Re: Idea for getting rid of VACUUM FREEZE on cold pages
Re: Idea for getting rid of VACUUM FREEZE on cold pages
List pgsql-hackers
On Thu, May 27, 2010 at 3:52 PM, Kevin Grittner
<Kevin.Grittner@wicourts.gov> wrote:
> Robert Haas <robertmhaas@gmail.com> wrote:
>> On Thu, May 27, 2010 at 3:15 PM, Kevin Grittner
>
>>> (a)  The tuples were written within the same transaction which
>>> created or truncated the table.
>
>> In case (a), you mess up visibility with respect to other
>> command-IDs within the transaction.
>
> Surely that problem is surmountable?

I proposed an idea at PGCon, but I believe Tom and Heikki thought it
was far too grotty to consider.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: functional call named notation clashes with SQL feature
Next
From: Tom Lane
Date:
Subject: Re: JSON manipulation functions