Skip site navigation (1) Skip section navigation (2)

pgsql: Fix DROP INDEX CONCURRENTLY IF EXISTS.

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 (view raw or flat)
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(-)

pgsql-committers by date

Next:From: Alvaro HerreraDate: 2012-08-27 18:31:21
Subject: pgsql: pg_upgrade: Fix exec_prog API to be less flaky
Previous:From: Bruce MomjianDate: 2012-08-27 13:31:58
Subject: pgsql: Have pgindent requre pg_bsd_indent version 1.2 now that a newve

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group