From: Andreas Karlsson <andreas@proxel.se>
To: Jim Nasby <Jim.Nasby@BlueTreble.com>
To: Michael Paquier <michael.paquier@gmail.com>
To: PostgreSQL mailing lists <pgsql-hackers@postgresql.org>
Subject: Re: REINDEX CONCURRENTLY 2.0
Date: Fri, 3 Mar 2017 03:44:49 +0100
Message-ID: <3ed671c8-0b03-e42a-710e-b50bb91b79fe@proxel.se> (raw)
In-Reply-To: <af867d20-1406-38c0-0a58-2cf1fce7240f@BlueTreble.com>
References: <CAB7nPqSTFkuc7dZxCDX4HOTU63YXHRroNv2aoUzyD-Zz_8Z_Zg@mail.gmail.com>
<a8e56251-bd3c-521e-7a2c-35d66b5f7f29@proxel.se>
<af867d20-1406-38c0-0a58-2cf1fce7240f@BlueTreble.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
On 03/02/2017 02:25 AM, Jim Nasby wrote:
> On 2/28/17 11:21 AM, Andreas Karlsson wrote:
>> The only downside I can see to this approach is that we no logner will
>> able to reindex catalog tables concurrently, but in return it should be
>> easier to confirm that this approach can be made work.
>
> Another downside is any stored regclass fields will become invalid.
> Admittedly that's a pretty unusual use case, but it'd be nice if there
> was at least a way to let users fix things during the rename phase
> (perhaps via an event trigger).
Good point, but I agree with Andres here. Having REINDEX CONCURRENTLY
issue event triggers seems strange to me. While it does create and drop
indexes as part of its implementation, it is actually just an index
maintenance job.
Andreas
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
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-hackers@postgresql.org
Cc: andreas@proxel.se, Jim.Nasby@BlueTreble.com, michael.paquier@gmail.com
Subject: Re: REINDEX CONCURRENTLY 2.0
In-Reply-To: <3ed671c8-0b03-e42a-710e-b50bb91b79fe@proxel.se>
* 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