Quick Links

Re: TRUNCATE SERIALIZABLE and frozen COPY

From:	Marti Raudsepp <marti(at)juffo(dot)org>
To:	Simon Riggs <simon(at)2ndquadrant(dot)com>
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 14:55:16
Message-ID:	CABRT9RCUJCCtF9rr5LT05BBiyQFBbUV3hcxfGnXP+nx793cZSA@mail.gmail.com
Views:	Raw Message \| Whole Thread \| Download mbox \| Resend email
Thread:
Lists:	pgsql-hackers

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? The latest one also invalidates any snapshots before earlier
truncates.

Regards,
Marti

In response to

Re: TRUNCATE SERIALIZABLE and frozen COPY at 2012-11-09 14:24:11 from Simon Riggs

Responses

Re: TRUNCATE SERIALIZABLE and frozen COPY at 2012-11-09 15:13:35 from Simon Riggs

Browse pgsql-hackers by date

	From	Date	Subject
Next Message	Alvaro Herrera	2012-11-09 15:08:20	Re: AutoVacuum starvation from sinval messages
Previous Message	Tom Lane	2012-11-09 14:50:36	Re: AutoVacuum starvation from sinval messages