Re: pgsql: Cache by-reference missing values in a long lived context

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Cache by-reference missing values in a long lived context
Date: 2023-08-25 13:40:14
Message-ID: 4126204.1692970814@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> On 2023-08-24 Th 16:57, Tom Lane wrote:
>> I'm not sure if those arguments justify a back-patch instead of
>> the localized hack you suggest.

> Seems like overkill given the age of the surrounding code and the
> nearness to EOL of releases 11 and 12.

I agree that 11 is nearly dead, but 12 still has a year-plus to go.

Another point that I wasn't thinking of yesterday is that 11 is
still expected to compile on pre-C99 compilers. I'm not sure
to what extent we are still able to test that -- my old animals
have all gone to buildfarm heaven, although I see that Noah's
AIX menagerie is still soldiering on. Were we relying on "{ 0 }"
anywhere else pre-v12?

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Andres Freund 2023-08-25 13:57:45 pgsql: Avoid non-POSIX cp flags
Previous Message Andrew Dunstan 2023-08-25 13:33:31 Re: pgsql: Cache by-reference missing values in a long lived context