| From: | Andreas Kretschmer <andreas(at)a-kretschmer(dot)de> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org,Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: [External] LIMIT not showing all results |
| Date: | 2019-03-05 18:06:07 |
| Message-ID: | 2A58A390-A362-41EF-99AB-0A5036189050@a-kretschmer.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 5 March 2019 18:54:33 CET, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>Andreas Kretschmer <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.
>
> regards, tom lane
yes, sounds reasonable.
Regards, Andreas.
--
2ndQuadrant - The PostgreSQL Support Company
--
2ndQuadrant - The PostgreSQL Support Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matthew Pounsett | 2019-03-05 18:09:28 | Re: [External] LIMIT not showing all results |
| Previous Message | Tom Lane | 2019-03-05 17:54:33 | Re: [External] LIMIT not showing all results |