pgsql: Fix DROP OPERATOR FAMILY IF EXISTS.

From: Robert Haas <rhaas(at)postgresql(dot)org>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix DROP OPERATOR FAMILY IF EXISTS.
Date: 2011-10-21 13:13:57
Message-ID: E1RHEv7-0001D1-P9@gemulon.postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Fix DROP OPERATOR FAMILY IF EXISTS.

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.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/980261929f2b8c40d6be1979ff81c943cad907b3

Modified Files
--------------
src/backend/commands/opclasscmds.c | 7 +++----
src/test/regress/expected/drop_if_exists.out | 2 +-
2 files changed, 4 insertions(+), 5 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Robert Haas 2011-10-21 17:40:49 pgsql: Try to log current the query string when a backend crashes.
Previous Message Tom Lane 2011-10-20 23:44:32 pgsql: Simplify and improve ProcessStandbyHSFeedbackMessage logic.