From: Andrey Klychkov <aaklychkov@mail.ru>
To: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Fwd: Re[2]: Alter index rename concurrently to
Date: Wed, 25 Jul 2018 14:46:14 +0300
Message-ID: <1532519174.453852573@f343.i.mail.ru> (raw)
Понедельник, 23 июля 2018, 18:06 +03:00 от Peter Eisentraut < peter.eisentraut@2ndquadrant.com >:
>
>You appear to be saying that you think that renaming an index
>concurrently is not safe
No, I didn't say it about renaming indexes.
I tried to say that it does not make sense exactly to rename a table (view, functions) concurrently
(and implement the lower lock level respectively) because probably no one will do this on production.
Because names of that objects are used in application's configuration.
I don't remember any cases I need to do this for tables but for indexes very often.
Renaming indexes is safe for client's applications because their names are not used in texts of SQL queries.
I think it's safe for relations too because, as we know, the database server works with indexes by using identifiers, not names.
Moreover, I tested it.
Ok, Peter, thanks for your answer!
--
Kind regards,
Andrey Klychkov
----------------------------------------------------------------------
--
Kind regards,
Andrey Klychkov
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: aaklychkov@mail.ru
Subject: Re: Fwd: Re[2]: Alter index rename concurrently to
In-Reply-To: <1532519174.453852573@f343.i.mail.ru>
* 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