From: | Ron <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: reindexing db |
Date: | 2020-12-08 06:59:08 |
Message-ID: | 39a8cdb5-bfbb-9ae8-5867-c4234373277c@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On 12/8/20 12:36 AM, Paul Förster wrote:
> Hi Ron,
>
>> On 08. Dec, 2020, at 06:42, Ron <ronljohnsonjr(at)gmail(dot)com> wrote:
>>
>> Changing subjects, but the thought of reindexing every index, whether it needs it or not, in one command, seems like a crime against database administration.
> 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.
>
> So, it's not a crime against database administration but rather a means of defense for a database administrator against an external crime attacking the database.
:) I understand that sometimes all tables *need* to be reindexed.
Probably a habit from my VAX/VMS days, but I prefer to enumerate every
table, not only for tracking but so that if the command fails 90% of the way
through, I can skip over the the completed portions.
--
Angular momentum makes the world go 'round.
From | Date | Subject | |
---|---|---|---|
Next Message | Paul Förster | 2020-12-08 07:21:27 | Re: reindexing db |
Previous Message | Paul Förster | 2020-12-08 06:36:19 | Re: reindexing db |