Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Subject: Re: reindexing db
From: Scott Ribe <scott_ribe@elevated-dev.com>
In-Reply-To: 
 <CAKFQuwb_6QWgSmUn-G2qEqmHWU1fychQuJrOZ_bF0ofCE0a_gg@mail.gmail.com>
Date: Mon, 7 Dec 2020 19:07:28 -0700
Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <7682F67C-0AA5-4CB7-BB46-42EAEC0C7DED@elevated-dev.com>
References: <292966DF-135C-4483-81A9-5027FC3C8A82@elevated-dev.com>
 <CAKFQuwb_6QWgSmUn-G2qEqmHWU1fychQuJrOZ_bF0ofCE0a_gg@mail.gmail.com>
To: "David G. Johnston" <david.g.johnston@gmail.com>
Precedence: bulk

> On Dec 7, 2020, at 6:00 PM, David G. Johnston =
<david.g.johnston@gmail.com> wrote:
>=20
> On Mon, Dec 7, 2020 at 5:45 PM Scott Ribe =
<scott_ribe@elevated-dev.com> wrote:
> Does reindexdb --concurrently skip over indexes for exclusion =
constraints, or reindex them separately without the concurrently option? =
The docs for reindexdb simply point one to the reindex docs for the =
caveats of concurrently, where that restriction is mentioned.
>=20
>=20
> The REINDEX page says:
>=20
> "Furthermore, indexes for exclusion constraints cannot be reindexed =
concurrently. If such an index is named directly in this command, an =
error is raised. If a table or database with exclusion constraint =
indexes is reindexed concurrently, those indexes will be skipped. (It is =
possible to reindex such indexes without the CONCURRENTLY option.)"

That is the sentence I was referring to, but it does not answer my =
question about what reindexdb does--whether it simply calls REINDEX =
DATABASE ..., or has logic to deal with this.