| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| 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:06:47 |
| Message-ID: | CAM3SWZQdRibwD1FmYTHjqgHUsA2oacEciU0=atUAROwf5ocaSA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On Wed, Mar 23, 2016 at 11:04 AM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
> 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.
I could get behind that if we really make an effort to help them make
an informed choice. The abbreviated keys optimization is highly
valuable, and I put a lot of work into it, as did Robert.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2016-03-23 18:09:53 | Re: Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5) |
| Previous Message | Magnus Hagander | 2016-03-23 18:04:44 | Re: Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2016-03-23 18:09:53 | Re: Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5) |
| Previous Message | Tom Lane | 2016-03-23 18:05:59 | Re: NOT EXIST for PREPARE |