Re: TRUNCATE SERIALIZABLE and frozen COPY

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Marti Raudsepp <marti(at)juffo(dot)org>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: TRUNCATE SERIALIZABLE and frozen COPY
Date: 2012-11-09 15:13:35
Message-ID: CA+U5nM+fs6u6hbRJiVJ41u=UrV0YgchhmWm03+3=8+LKxgmh5A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 9 November 2012 14:55, Marti Raudsepp <marti(at)juffo(dot)org> wrote:
> On Fri, Nov 9, 2012 at 4:24 PM, Simon Riggs <simon(at)2ndquadrant(dot)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?

Yes

> The latest one also invalidates any snapshots before earlier
> truncates.

1 per table, arbirary number of tables

--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2012-11-09 15:18:05 Re: WIP checksums patch
Previous Message Robert Haas 2012-11-09 15:13:01 Re: AutoVacuum starvation from sinval messages