Parser bug (?) - Mailing list pgsql-hackers

From Oliver Elphick
Subject Parser bug (?)
Date
Msg-id 199812051957.TAA23366@linda.lfix.co.uk
Whole thread Raw
Responses Re: [HACKERS] Parser bug (?)  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: [HACKERS] Parser bug (?)  (Bruce Momjian <maillist@candle.pha.pa.us>)
List pgsql-hackers
Hi Tom,

This looks like a parser bug in 6.4.  I found it while trying to run
pg_upgrade:

bray=> create table junk ("singleton" "char");
CREATE
bray=> drop table junk;
DROP
bray=> create table junk ("singleton" "char" default 'M');
ERROR:  DEFAULT: const type mismatched
bray=> create table junk ("singleton" char default 'M');
CREATE

pg_dump puts all type names in double quotes, which triggers this bug
when pg_upgrade is run, with the result that the upgrade fails.

[Machine is i686 Linux 2.1.125 with glibc 2.0.7u]

-- 
Oliver Elphick                                Oliver.Elphick@lfix.co.uk
Isle of Wight                              http://www.lfix.co.uk/oliver              PGP key from public servers; key
ID32B8FAA1                ========================================    "Go ye therefore, and teach all nations,
baptizingthem     in the name of the Father, and of the Son, and of the      Holy Ghost; Teaching them to observe all
things      whatsoever I have commanded you; and, lo, I am with      you alway, even unto the end of the world. Amen."
             Matthew 28:19,20 
 




pgsql-hackers by date:

Previous
From: Constantin Teodorescu
Date:
Subject: Re: [HACKERS] pg_dump - segfault with -z option
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] Patch for pg_dump (6.4) inheritance bug