Re: Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5)
От | Peter Geoghegan |
---|---|
Тема | Re: Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5) |
Дата | |
Msg-id | CAM3SWZRodZbhYK=-kVK003pUE8ZknUgni454VWhNg0HrQ5j8+Q@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5) (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5)
|
Список | pgsql-bugs |
On Thu, Mar 24, 2016 at 12:20 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: >> The only people that are likely comfortable giving final sign-off on >> it that are active this CF are Tom and Kevin. That is an awkward >> situation. > > I would not be comfortable with reviewing an entire module with the > intention of shipping it in a stable branch on Monday, even if I had > nothing else to do between now and then. I think the only sane way > to get this into 9.5.2 would be to slip the release date, and that > seems rather counterproductive. We need to get this fix into the > hands of users ASAP. That's fair. I didn't really imagine that we'd want to put the tool into 9.5 myself. Still, I think that amcheck could have some role to play in managing the problem. Even the near-term availability of amcheck for 9.5 as a satellite project would count. That could happen without blocking the point release. I just don't want to go over anyone's head with that. "REINDEX everything" isn't a realistic plan for a lot of users. -- Peter Geoghegan
В списке pgsql-bugs по дате отправления: