Re: Idea for getting rid of VACUUM FREEZE on cold pages

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Robert Haas" <robertmhaas(at)gmail(dot)com>
Cc: "Josh Berkus" <josh(at)agliodbs(dot)com>, "Jesper Krogh" <jesper(at)krogh(dot)cc>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Idea for getting rid of VACUUM FREEZE on cold pages
Date: 2010-05-27 19:52:35
Message-ID: 4BFE87330200002500031B94@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)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?

-Kevin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2010-05-27 19:53:35 Re: Synchronization levels in SR
Previous Message Tom Lane 2010-05-27 19:50:33 Re: JSON manipulation functions