Re: Inconsistent error message wording for REINDEX CONCURRENTLY
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2019-05-09T04:11:54Z
Lists: pgsql-hackers
Attachments
- reindex-catalog-errors-v3.patch (text/x-diff) patch v3
On Wed, May 08, 2019 at 11:28:35PM -0400, Tom Lane wrote: > Michael Paquier <michael@paquier.xyz> writes: >> No problem to do that. I'll brush up all that once you commit the >> first piece you have come up with, and reuse the new API of catalog.c >> you are introducing based on the table OID. > > Pushed my stuff, have at it. Thanks. Attached is what I get to after scanning the error messages in indexcmds.c and index.c. Perhaps you have more comments about it? -- Michael
Commits
-
Rework some error strings for REINDEX CONCURRENTLY with system catalogs
- 20e1cc898da6 12.0 landed
-
Improve and fix some error handling for REINDEX INDEX/TABLE CONCURRENTLY
- 508300e2e141 12.0 landed
-
Clean up the behavior and API of catalog.c's is-catalog-relation tests.
- 2d7d946cd323 12.0 landed