| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Noah Misch <noah(at)leadboat(dot)com>, pgsql-committers(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] pgsql: Improve performance of SendRowDescriptionMessage. |
| Date: | 2017-10-13 18:24:05 |
| Message-ID: | 20171013182405.7smzzv3vw67o2fjy@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2017-10-13 19:09:12 | pgsql: Fix possible crash with Parallel Bitmap Heap Scan. |
| Previous Message | Tom Lane | 2017-10-13 18:19:22 | Re: [HACKERS] pgsql: Improve performance of SendRowDescriptionMessage. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-10-13 18:27:45 | Re: Improve catcache/syscache performance. |
| Previous Message | Tom Lane | 2017-10-13 18:19:22 | Re: [HACKERS] pgsql: Improve performance of SendRowDescriptionMessage. |