Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commite323c55

Browse files
committed
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 commit8cb5365.Per report from Brendan Byrd.
1 parente40bddb commite323c55

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

‎src/backend/parser/gram.y

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4941,7 +4941,7 @@ DropStmt:DROP drop_type IF_P EXISTS any_name_list opt_drop_behavior
49414941
{
49424942
DropStmt *n = makeNode(DropStmt);
49434943
n->removeType = OBJECT_INDEX;
4944-
n->missing_ok =FALSE;
4944+
n->missing_ok =TRUE;
49454945
n->objects =$6;
49464946
n->arguments = NIL;
49474947
n->behavior =$7;

‎src/test/regress/expected/create_index.out

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2321,7 +2321,7 @@ Indexes:
23212321
--
23222322
DROP INDEX CONCURRENTLY "concur_index2";-- works
23232323
DROP INDEX CONCURRENTLY IF EXISTS "concur_index2";-- notice
2324-
ERROR: index "concur_index2" does not exist
2324+
NOTICE: index "concur_index2" does not exist, skipping
23252325
-- failures
23262326
DROP INDEX CONCURRENTLY "concur_index2", "concur_index3";
23272327
ERROR: DROP INDEX CONCURRENTLY does not support dropping multiple objects

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp