1berry/postgres
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix DROP OPERATOR FAMILY IF EXISTS.

Browse Source 
Essentially, the "IF EXISTS" portion was being ignored, and an error
thrown anyway if the opfamily did not exist.

I broke this in commit fd1843ff8979c0461fb3f1a9eab61140c977e32d; so
backpatch to 9.1.X.

Report and diagnosis by KaiGai Kohei.
This commit is contained in:
Robert Haas 2011-10-21 09:10:46 -04:00
parent d1d094e4cf
commit 5c5138f2f8
1 changed files with 3 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
src/backend/commands/opclasscmds.c
View File

@ -1614,9 +1614,8 @@ RemoveOpFamily(RemoveOpFamilyStmt *stmt)
tuple = OpFamilyCacheLookup(amID, stmt->opfamilyname, stmt->missing_ok); tuple = OpFamilyCacheLookup(amID, stmt->opfamilyname, stmt->missing_ok);
if (!HeapTupleIsValid(tuple)) if (!HeapTupleIsValid(tuple))
{ {
ereport(ERROR, ereport(NOTICE,
(errcode(ERRCODE_UNDEFINED_OBJECT), (errmsg("operator family \"%s\" does not exist for access method \"%s\", skipping",
errmsg("operator family \"%s\" does not exist for access method \"%s\"",
NameListToString(stmt->opfamilyname), stmt->amname))); NameListToString(stmt->opfamilyname), stmt->amname)));
return; return;
} }