Re: [External] LIMIT not showing all results
От | Andreas Kretschmer |
---|---|
Тема | Re: [External] LIMIT not showing all results |
Дата | |
Msg-id | bdf341c5-a671-e511-247e-66b7f8b6de10@a-kretschmer.de обсуждение исходный текст |
Ответ на | Re: [External] LIMIT not showing all results (Matthew Pounsett <matt@conundrum.com>) |
Список | pgsql-general |
Am 05.03.19 um 19:09 schrieb Matthew Pounsett: > > > On Tue, 5 Mar 2019 at 12:54, Tom Lane <tgl@sss.pgh.pa.us > <mailto:tgl@sss.pgh.pa.us>> wrote: > > Andreas Kretschmer <andreas@a-kretschmer.de > <mailto:andreas@a-kretschmer.de>> writes: > > the other thing is, it would be nice to to know why the index is > corrupt. > > Given that (a) this was triggered by a server migration and (b) > the leading column of the index looks like it's probably varchar, > I'm suspicious that the new server has different collation behavior. > > > The migration in question was an rsync from a Debian 9 box > running 9.4.19-0+deb8u1 to a FreeBSD 11 box running 9.4.20. yeah, check and compare the glibc - version on both systems. (ldd --version) Regards, Andreas -- 2ndQuadrant - The PostgreSQL Support Company. www.2ndQuadrant.com
В списке pgsql-general по дате отправления: