Re: [HACKERS] [COMMITTERS] pgsql: Improve performance ofSendRowDescriptionMessage. - Mailing list pgsql-committers

From Andres Freund
Subject Re: [HACKERS] [COMMITTERS] pgsql: Improve performance ofSendRowDescriptionMessage.
Date
Msg-id 20171013182405.7smzzv3vw67o2fjy@alap3.anarazel.de
Whole thread Raw
In response to Re: [HACKERS] [COMMITTERS] pgsql: Improve performance of SendRowDescriptionMessage.  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] [COMMITTERS] pgsql: Improve performance of SendRowDescriptionMessage.
List pgsql-committers
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.

Greetings,

Andres Freund


-- 
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers

pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] [COMMITTERS] pgsql: Improve performance of SendRowDescriptionMessage.
Next
From: Robert Haas
Date:
Subject: [COMMITTERS] pgsql: Fix possible crash with Parallel Bitmap Heap Scan.