pgsql: Fix DROP INDEX CONCURRENTLY IF EXISTS. - Mailing list pgsql-committers

From Tom Lane
Subject pgsql: Fix DROP INDEX CONCURRENTLY IF EXISTS.
Date
Msg-id E1T62Rx-0007Fa-Ji@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Fix DROP INDEX CONCURRENTLY IF EXISTS.

This threw ERROR, not the expected NOTICE, if the index didn't exist.
The bug was actually visible in not-as-expected regression test output,
so somebody wasn't paying too close attention in commit
8cb53654dbdb4c386369eb988062d0bbb6de725e.
Per report from Brendan Byrd.

Branch
------
REL9_2_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/a6f43529ea6c3abd9207cea140ab231ac078746a

Modified Files
--------------
src/backend/parser/gram.y                  |    2 +-
src/test/regress/expected/create_index.out |    2 +-
2 files changed, 2 insertions(+), 2 deletions(-)


pgsql-committers by date:

Previous
From: Bruce Momjian
Date:
Subject: pgsql: Have pgindent requre pg_bsd_indent version 1.2 now that a new ve
Next
From: Tom Lane
Date:
Subject: pgsql: Fix DROP INDEX CONCURRENTLY IF EXISTS.