Greg Stark wrote: > Bruce Momjian <pgman@xxxxxxxxxxxxxxxx> writes: > > > > What happens if someone already has a type called "e" ? > > > > That would be the same problem as someone having a type 'b' or 'x'. It > > would still work, but not for casts like text'str'. Those letters are > > caught in the lexer before getting into to the parser. > > What I'm asking about is, are there going to be user applications that were > working fine in previous versions but suddenly start breaking when this change > is made? Does that affect your decision in whether to backport this to 8.0.x? The use of "E" as a data type that is used as E'' seems pretty rare, but I suppose it is possible. We really haven't even discussed the idea of backporting anything, it is just an open issue at the time we release an 8.0.X. -- Bruce Momjian | http://candle.pha.pa.us pgman@xxxxxxxxxxxxxxxx | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
