Bug in CREATE OPERATOR - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject Bug in CREATE OPERATOR
Date
Msg-id NEBBIOAJBMEENKACLNPCIELICCAA.chriskl@familyhealth.com.au
Whole thread Raw
Responses RE: Bug in CREATE OPERATOR  ("Darren King" <darrenk@insightdist.com>)
Re: Bug in CREATE OPERATOR  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
As part of our development, one of our programmers created a new database
type, plus operators and functions to go with it.  One of the things he did
was this:

CREATE OPERATOR testbit (   leftarg = bitset,   rightarg = int4,   procedure = testbit,   commutator = testbit
);

Notice that this is an ILLEGAL type - the name of the type (from docs) must
only contain these characters:

+ - * / < > = ~ ! @ # % ^ & | ` ? $

However, PostgreSQL 7.0.3 went right ahead and created the operator anyway!!

Now we have a big problem, as the DROP OPERATOR command cannot delete the
illegally named operator.

eg:

usa=# drop operator testbit (bitset, int4);
ERROR:  parser: parse error at or near "testbit "
usa=# drop operator 'testbit ' (bitset, int4);
ERROR:  parser: parse error at or near "'"
usa=# drop operator "testbit " (bitset, int4);
ERROR:  parser: parse error at or near """

We can't delete it!!!  I also assume that it was a bug that it could even be
created in the first place...

Chris

--
Christopher Kings-Lynne
Family Health Network (ACN 089 639 243)



pgsql-hackers by date:

Previous
From: Karel Zak
Date:
Subject: PL/Python (was: Re: [GENERAL] Re: Trigger)
Next
From: Tatsuo Ishii
Date:
Subject: sequence numbering on mails