Re: Re: [COMMITTERS] 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 <robertmhaas(at)gmail(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: [COMMITTERS] pgsql: Prevent "snapshot too old" from trying to return pruned TOAST tu
Date: 2016-08-05 15:05:31
Message-ID: 5831.1470409531@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Thu, Aug 4, 2016 at 10:58 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> What is the reason? We refuse to separate frontend and backend
>> headers in any sort of principled way?

> That was poorly phrased. I'll try again: I can't see any reason for
> using a macro here except that it allows frontend code to compile this
> without breaking.

Well, the alternative would be to put "#ifndef FRONTEND" around the
static-inline function. That's not very pretty either, and it's
inconsistent with the existing precedent (ie, InitDirtySnapshot).
Also, it presumes that a non-backend includer actually has defined
FRONTEND; that seems to be the case for pg_xlogdump but I do not
think we do that everywhere.

> Here's a patch. Is this what you want?

OK by me.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Robert Haas 2016-08-05 16:04:12 pgsql: Change InitToastSnapshot to a macro.
Previous Message Robert Haas 2016-08-05 03:59:06 Re: [COMMITTERS] pgsql: Prevent "snapshot too old" from trying to return pruned TOAST tu

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2016-08-05 15:06:15 Re: pg_size_pretty, SHOW, and spaces
Previous Message Petr Jelinek 2016-08-05 15:00:13 Logical Replication WIP