From: | Peter Geoghegan <pg(at)heroku(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, Marc-Olaf Jaschke <marc-olaf(dot)jaschke(at)s24(dot)com>, Postgres-Bugs <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5) |
Date: | 2016-03-23 17:52:14 |
Message-ID: | CAM3SWZSDVO_4tyDPgYX5NWFW=3BcCLpHV-vUtKKJ-VryqoKjVQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
On Wed, Mar 23, 2016 at 10:46 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> If I had to make a recommendation right now, I would go for your
> option #4, ie shut 'em all down Scotty. We do not know the full extent
> of the problem but it looks pretty bad, and I think our first priority
> has to be to guarantee data integrity.
+1, but only for glibc, and configurable. The glibc default might
later be revisited in the stable 9.5 branch.
--
Peter Geoghegan
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2016-03-23 17:56:32 | Re: Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5) |
Previous Message | Tom Lane | 2016-03-23 17:46:52 | Re: Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5) |
From | Date | Subject | |
---|---|---|---|
Next Message | Petr Jelinek | 2016-03-23 17:52:51 | Re: Proposal: Generic WAL logical messages |
Previous Message | Tom Lane | 2016-03-23 17:46:52 | Re: Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5) |