Re: TRUNCATE SERIALIZABLE and frozen COPY - Mailing list pgsql-hackers

From Marti Raudsepp
Subject Re: TRUNCATE SERIALIZABLE and frozen COPY
Date
Msg-id CABRT9RCUJCCtF9rr5LT05BBiyQFBbUV3hcxfGnXP+nx793cZSA@mail.gmail.com
Whole thread Raw
In response to Re: TRUNCATE SERIALIZABLE and frozen COPY  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: TRUNCATE SERIALIZABLE and frozen COPY  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
On Fri, Nov 9, 2012 at 4:24 PM, Simon Riggs <simon@2ndquadrant.com> wrote:
> We need a fast lookup structure that is expandable to accommodate
> arbitrary numbers of truncates. Shared hash table, with some form of
> overflow mechanism.

Surely you only need to remember the last completed truncate for each
relation? The latest one also invalidates any snapshots before earlier
truncates.

Regards,
Marti



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: AutoVacuum starvation from sinval messages
Next
From: Alvaro Herrera
Date:
Subject: Re: AutoVacuum starvation from sinval messages