Re: pgsql: Refactor code in tablecmds.c to check and process tablespace mov

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Refactor code in tablecmds.c to check and process tablespace mov
Date: 2021-01-29 05:05:33
Message-ID: YBOXna5PZ6xe+gEo@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Thu, Jan 28, 2021 at 10:56:29AM -0300, Alvaro Herrera wrote:
> Yep, seems OK to me, assuming that, as you say, you'll update the
> comments again when they are used to handle the concurrent cases.

That's the idea. I need first to look in depth at what's proposed on
the other thread for REINDEX, but I see no reason why the case of
REINDEX CONCURRENTLY would not be able to use this stuff. Applied
this part for now. Thanks.
--
Michael

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Paquier 2021-01-29 05:32:04 pgsql: doc: Improve wording of section for repslot statistics
Previous Message Michael Paquier 2021-01-29 05:02:25 pgsql: Adjust comments of CheckRelationTableSpaceMove() and SetRelation