Re: pgsql: Prevent "snapshot too old" from trying to return pruned TOAST tu

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <rhaas(at)postgresql(dot)org>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Prevent "snapshot too old" from trying to return pruned TOAST tu
Date: 2016-08-04 23:23:26
Message-ID: 26768.1470353006@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Robert Haas <rhaas(at)postgresql(dot)org> writes:
> Prevent "snapshot too old" from trying to return pruned TOAST tuples.

Looks like this patch broke the build on castoroides. Recommend
changing InitToastSnapshot into a macro. (There's a reason why
InitDirtySnapshot is a macro.)

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Robert Haas 2016-08-05 02:58:28 Re: pgsql: Prevent "snapshot too old" from trying to return pruned TOAST tu
Previous Message Bruce Momjian 2016-08-04 22:55:55 pgsql: docs: mention rsync of temp and unlogged tables

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2016-08-04 23:31:28 Re: Heap WARM Tuples - Design Draft
Previous Message Peter Geoghegan 2016-08-04 23:09:17 Re: Possible duplicate release of buffer lock.