| From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | Colin Adler <colin(at)coder(dot)com>, pgsql-general General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Query returns no results until REINDEX |
| Date: | 2020-02-11 20:13:41 |
| Message-ID: | CAOBaU_brh5vctfa+9nAo-u2URL7HKE-deFoZnVrb8=9ydD1jGQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Feb 11, 2020 at 8:33 PM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
>
> On Sun, Feb 9, 2020 at 12:50 PM Colin Adler <colin(at)coder(dot)com> wrote:
> > Looks like it found something. I checked out the contrib/pageinspect docs but
> > wasn't too sure what to run. Are incompatible libc versions causing btree
> > corruption something you consider a bug? If it's something you'd like to look
> > into further I can gladly send over the database files.
>
> No, this is not considered a bug.
>
> It's unfortunate that there is no built in collation versioning
> mechanism, or something like that -- that might have alerted you to
> the problem before any real damage occurred.
FTR, this is something being actively worked on [1], and I still hope
that in pg13 a glibc or ICU upgrade will be detected and raise proper
warning.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrus | 2020-02-11 22:26:50 | How to restore roles without changing postgres password |
| Previous Message | Peter Geoghegan | 2020-02-11 19:32:35 | Re: Query returns no results until REINDEX |