| From: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
|---|---|
| To: | Paul Förster <paul(dot)foerster(at)gmail(dot)com> |
| Cc: | Ron <ronljohnsonjr(at)gmail(dot)com>, pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: reindexing db |
| Date: | 2020-12-08 13:32:34 |
| Message-ID: | 5188016F-8C58-47C6-8A15-913A6C123263@elevated-dev.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
> On Dec 7, 2020, at 11:36 PM, Paul Förster <paul(dot)foerster(at)gmail(dot)com> wrote:
>
> hmm, yes, I agree to *some* point. But also think about possible changes in glibc and the collation problems corrupting indexes that come with it. So, you do a reindexdb deliberately to protect yourself against index corruption because PostgreSQL can't know by itself that it needs such protection because it doesn't know of any changes in glibc.
This is exactly why I'm doing it.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron | 2020-12-08 14:26:02 | Re: reindexing db |
| Previous Message | Paul Förster | 2020-12-08 10:01:21 | Re: reindexing db |