Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.20.0.2.21\))
Subject: Re: reindexing db
From: =?utf-8?Q?Paul_F=C3=B6rster?= <paul.foerster@gmail.com>
In-Reply-To: <f477709e-6371-1ba3-84df-37e5df8e5d83@gmail.com>
Date: Tue, 8 Dec 2020 07:36:19 +0100
Cc: pgsql-admin@lists.postgresql.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <214E5DBC-1F6F-49C1-8B83-9A2EB33E969A@gmail.com>
References: <292966DF-135C-4483-81A9-5027FC3C8A82@elevated-dev.com>
 <f477709e-6371-1ba3-84df-37e5df8e5d83@gmail.com>
To: Ron <ronljohnsonjr@gmail.com>
Precedence: bulk

Hi Ron,

> On 08. Dec, 2020, at 06:42, Ron <ronljohnsonjr@gmail.com> wrote:
>=20
> 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.

Cheers,
Paul=