Postgres Pro
Downloads
Home   >   mailing lists

Re: pgsql: Prevent "snapshot too old" from trying to return pruned TOAST tu - Mailing list pgsql-committers

From Robert Haas
Subject Re: pgsql: Prevent "snapshot too old" from trying to return pruned TOAST tu
Date
Msg-id CA+TgmobB_gM57=aUfqqbkc4g+K3_pNAX+StJSn0nXZLH9LROjg@mail.gmail.com
Whole thread Raw
In response to Re: pgsql: Prevent "snapshot too old" from trying to return pruned TOAST tu  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-committers
Tree view 
On Thu, Aug 4, 2016 at 7:23 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <rhaas@postgresql.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.)

What is the reason?  We refuse to separate frontend and backend
headers in any sort of principled way?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pgsql: Prevent "snapshot too old" from trying to return pruned TOAST tu
Next
From: Andres Freund
Date:
Subject: pgsql: Fix hard to hit race condition in heapam's tuple locking code.