From: Scott Ribe <scott_ribe@elevated-dev.com>
To: Paul Förster <paul.foerster@gmail.com>
Cc: Ron <ronljohnsonjr@gmail.com>
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: reindexing db
Date: Tue, 8 Dec 2020 06:32:34 -0700
Message-ID: <5188016F-8C58-47C6-8A15-913A6C123263@elevated-dev.com> (raw)
In-Reply-To: <214E5DBC-1F6F-49C1-8B83-9A2EB33E969A@gmail.com>
References: <292966DF-135C-4483-81A9-5027FC3C8A82@elevated-dev.com>
<f477709e-6371-1ba3-84df-37e5df8e5d83@gmail.com>
<214E5DBC-1F6F-49C1-8B83-9A2EB33E969A@gmail.com>
> On Dec 7, 2020, at 11:36 PM, Paul Förster <paul.foerster@gmail.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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: scott_ribe@elevated-dev.com, paul.foerster@gmail.com, ronljohnsonjr@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: reindexing db
In-Reply-To: <5188016F-8C58-47C6-8A15-913A6C123263@elevated-dev.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox