Re: Confusing error message for REINDEX TABLE CONCURRENTLY - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Confusing error message for REINDEX TABLE CONCURRENTLY
Date
Msg-id 20190605061113.GG1580@paquier.xyz
Whole thread Raw
In response to Re: Confusing error message for REINDEX TABLE CONCURRENTLY  (Ashwin Agrawal <aagrawal@pivotal.io>)
Responses Re: Confusing error message for REINDEX TABLE CONCURRENTLY
List pgsql-hackers
On Tue, Jun 04, 2019 at 11:26:44AM -0700, Ashwin Agrawal wrote:
> The variable is used in else scope hence I moved it there. But yes its
> removed completely for this scope.

Thanks for updating the patch.  It does its job by having one separate
message for the concurrent and the non-concurrent cases as discussed.
David, what do you think?  Perhaps you would like to commit it
yourself?
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: nitpick about poor style in MergeAttributes
Next
From: tushar
Date:
Subject: Re: [pg_rewind] cp: cannot stat ‘pg_wal/RECOVERYHISTORY’: No such file or directory