Re: [HACKERS] Beta for 4:30AST ... ? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] Beta for 4:30AST ... ?
Date
Msg-id 1422.951286471@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] Beta for 4:30AST ... ?  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: [HACKERS] Beta for 4:30AST ... ?  (Peter Eisentraut <e99re41@DoCS.UU.SE>)
Re: [HACKERS] Beta for 4:30AST ... ?  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
Bruce Momjian <pgman@candle.pha.pa.us> writes:
>> Somehow you have to do something similar to
>> insert OID = 9999 ( bit varying PGUID 1 1 t b t \054 0 0 bitvaryingin ... )

> Huh, I still don't get it.  What is the matter with that insert?

The space in the type name is gonna confuse things.

>> And no, naming the type bit_varying internally is not an acceptable
>> answer. ;) We might want to start thinking about this item before national
>> character comes our way. (Or just document the solution, if it already
>> exists.)

AFAICS the solution would have to be similar to what we already do for
CHARACTER VARYING: parse the type declaration specially in gram.y,
and translate it to an internal type name.

gram.y already knows about NATIONAL CHARACTER [ VARYING ] too, BTW.
Seems to just translate it into bpchar or varchar :-( ... but the
syntax problem is solved.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: about 7.0 LIMIT optimization
Next
From: "Vladimír Beneš"
Date:
Subject: Re: [HACKERS] Out of memory problem (forwarded bug report)