| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Peter Geoghegan <pg(at)heroku(dot)com> |
| Cc: | Noah Misch <noah(at)leadboat(dot)com>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>, Marc-Olaf Jaschke <marc-olaf(dot)jaschke(at)s24(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5) |
| Date: | 2016-03-23 18:04:44 |
| Message-ID: | CABUevEz09i3YpEbLkV6JXSeYZs2e-yFYh9Ui1-cT2r=K72fFBQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On Wed, Mar 23, 2016 at 6:58 PM, Peter Geoghegan <pg(at)heroku(dot)com> wrote:
> On Wed, Mar 23, 2016 at 10:56 AM, Magnus Hagander <magnus(at)hagander(dot)net>
> wrote:
> > Are you talking about configurable at./configure time, or guc?
>
> I meant a GUC. I think a ./configure option is overkill.
>
We clearly have different views of the amount of kill effort required for
the different options :) I would've said that a ./configure option is the
easier way, and that doing a GUC is the one that's an overkill (being
significantly more effort).
That said, my main point is that I do not think the knob is something that
should be tuned by the average end user. For most people, that should be
left to the packagers for the platform, who can make an informed choice
about if it's safe to turn it on.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2016-03-23 18:06:47 | Re: Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5) |
| Previous Message | Peter Geoghegan | 2016-03-23 18:02:32 | Re: Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-03-23 18:05:59 | Re: NOT EXIST for PREPARE |
| Previous Message | Peter Geoghegan | 2016-03-23 18:02:32 | Re: Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5) |