From: Andres Freund <andres@anarazel.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Noah Misch <noah@leadboat.com>
Cc: pgsql-committers@postgresql.org
Subject: Re: [HACKERS] [COMMITTERS] pgsql: Improve performance of SendRowDescriptionMessage.
Date: Sat, 13 Aug 2022 12:08:43 -0700
Message-ID: <20220813190843.wrs3feelaxy434un@awork3.anarazel.de> (raw)
In-Reply-To: <20171013182405.7smzzv3vw67o2fjy@alap3.anarazel.de>
References: <307.1507819498@sss.pgh.pa.us>
<20171012230844.ye4tnye2shysvqpk@alap3.anarazel.de>
<20171013023536.GA492146@rfd.leadboat.com>
<12267.1507862660@sss.pgh.pa.us>
<20171013070247.GA505228@rfd.leadboat.com>
<21773.1507908395@sss.pgh.pa.us>
<530.1507916887@sss.pgh.pa.us>
<20171013180106.ruju5qtn6xpw45us@alap3.anarazel.de>
<1820.1507918762@sss.pgh.pa.us>
<20171013182405.7smzzv3vw67o2fjy@alap3.anarazel.de>
Hi Noah,
On 2017-10-13 11:24:05 -0700, Andres Freund wrote:
> On 2017-10-13 14:19:22 -0400, Tom Lane wrote:
> > > So it'd probably better to introduce a FORCE_DISABLE_RESTRICT=yes, set
> > > at the same place, that's then tested before running the relevant
> > > configure check?
> >
> > +1. I think you don't actually have to skip the configure check,
> > and there might be some value in letting it carry on normally
> > (so that "restrict" is set properly). We'd just want it to affect
> > what pg_restrict gets defined as. Something like
>
> > if test "$ac_cv_c_restrict" = "no" -o "x$FORCE_DISABLE_RESTRICT" = "xyes"; then
> > pg_restrict=""
> > else
> > pg_restrict="$ac_cv_c_restrict"
>
> Yea, that works. Will make it so.
Any chance you could check if this is still needed? I've a FIXME about it in
the meson code that I'd like to get rid of :)
Greetings,
Andres Freund
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-committers@postgresql.org
Cc: andres@anarazel.de, tgl@sss.pgh.pa.us, noah@leadboat.com
Subject: Re: [HACKERS] [COMMITTERS] pgsql: Improve performance of SendRowDescriptionMessage.
In-Reply-To: <20220813190843.wrs3feelaxy434un@awork3.anarazel.de>
References: <307.1507819498@sss.pgh.pa.us> <20171012230844.ye4tnye2shysvqpk@alap3.anarazel.de> <20171013023536.GA492146@rfd.leadboat.com> <12267.1507862660@sss.pgh.pa.us> <20171013070247.GA505228@rfd.leadboat.com> <21773.1507908395@sss.pgh.pa.us> <530.1507916887@sss.pgh.pa.us> <20171013180106.ruju5qtn6xpw45us@alap3.anarazel.de> <1820.1507918762@sss.pgh.pa.us> <20171013182405.7smzzv3vw67o2fjy@alap3.anarazel.de> <20220813190843.wrs3feelaxy434un@awork3.anarazel.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox