Bug with sequences in 6.4.2

From: wehner(at)digital-security(dot)com (Stefan Wehner)
To: pgsql-general(at)postgreSQL(dot)org
Subject: Bug with sequences in 6.4.2
Date: 1999-03-11 13:22:12
Message-ID: 19990311132212.EDB3815186@miraculix.shw.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Greetings,
there seems to be a slight bug in the parsing of the
nextval function, tested under 6.4.2.
It affects also the SERIAL type.

Symptom :

CREATE SEQUENCE "AA";
-- Correct, quoted identifier is allowed;
SELECT NEXTVAL('AA');
--Produces Error
--aa.nextval: sequence does not exist

Probable source of problem, the Argument to nextval is
not handled correctly as an Table Identifier.

E.g. nextval('"AA"') is generates
"aa".nextval: sequence does not exist

Note the lowercase between the quotes.

I quickly browsed the sources, but have not found the
place where the conversion to lowercase occurs.

Please check this against 6.5 and 6.4.3 too.

With Regards,
Stefan Wehner

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tim Röstermundt 1999-03-11 13:33:28 Postgres-dump with binary data!
Previous Message Stefan Wehner 1999-03-11 12:39:05 Bug in Sequences [6.4.2]

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 1999-03-11 15:56:26 Binary-compatible types vs. overloaded operators
Previous Message Oleg Broytmann 1999-03-11 12:48:12 RE: [HACKERS] Bug on complex subselect (was: Bug on complex join)