| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql: Fix DROP INDEX CONCURRENTLY IF EXISTS. |
| Date: | 2012-08-27 16:46:05 |
| Message-ID: | E1T62Rx-0007FY-If@gemulon.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
------
master
Details
-------
http://git.postgresql.org/pg/commitdiff/e323c553017601597b6a5f9f19426587df512ad9
Modified Files
--------------
src/backend/parser/gram.y | 2 +-
src/test/regress/expected/create_index.out | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2012-08-27 18:31:21 | pgsql: pg_upgrade: Fix exec_prog API to be less flaky |
| Previous Message | Bruce Momjian | 2012-08-27 13:31:58 | pgsql: Have pgindent requre pg_bsd_indent version 1.2 now that a new ve |