]> granicus.if.org Git - postgresql/commit
Fix confusing NOTICE text in REINDEX CONCURRENTLY
authorDavid Rowley <drowley@postgresql.org>
Wed, 5 Jun 2019 09:05:41 +0000 (21:05 +1200)
committerDavid Rowley <drowley@postgresql.org>
Wed, 5 Jun 2019 09:05:41 +0000 (21:05 +1200)
commite24a815c1c8550fcba5cc5aeb0d130db46570872
tree8ceb00adb8eb3f6f7af840e9ee17f5f415a39d06
parent56b3b3838284f53c83556592e60688522155f57f
Fix confusing NOTICE text in REINDEX CONCURRENTLY

When performing REINDEX TABLE CONCURRENTLY, if all of the table's indexes
could not be reindexed, a NOTICE message claimed that the table had no
indexes.  This was confusing, so let's change the NOTICE text to something
less confusing.

In passing, also mention in the comment before ReindexRelationConcurrently
that materialized views are supported too and also explain what the return
value of the function means.

Author: Ashwin Agrawal
Reviewed-by: Michael Paquier
Discussion: https://postgr.es/m/CALfoeithHvi13p_VyR8kt9o6Pa7Z=Smi6Nfc2anHnQx5Lj8bTQ@mail.gmail.com
src/backend/commands/indexcmds.c
src/test/regress/expected/create_index.out