| From: | Andreas Kretschmer <andreas(at)a-kretschmer(dot)de> |
|---|---|
| To: | Matthew Pounsett <matt(at)conundrum(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: [External] LIMIT not showing all results |
| Date: | 2019-03-05 18:43:18 |
| Message-ID: | bdf341c5-a671-e511-247e-66b7f8b6de10@a-kretschmer.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Am 05.03.19 um 19:09 schrieb Matthew Pounsett:
>
>
> On Tue, 5 Mar 2019 at 12:54, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us
> <mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us>> wrote:
>
> Andreas Kretschmer <andreas(at)a-kretschmer(dot)de
> <mailto:andreas(at)a-kretschmer(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Kretschmer | 2019-03-05 18:44:05 | Re: LIMIT not showing all results |
| Previous Message | Casey Deccio | 2019-03-05 18:41:08 | Re: LIMIT not showing all results |