Re: @(#) Mordred Labs advisory 0x0001: Buffer overflow in

"Zeugswetter Andreas SB SD" <ZeugswetterA@spardat.at> writes:
>> "Zeugswetter Andreas SB SD" <ZeugswetterA@spardat.at> writes:
>>> Hard to say what is good for those names imho, don't like 
>>> "anytype" :-(
>> 
>> How about "any"?  It's a reserved word per SQL99, I think.

> I would actually stick to opaque in that case, already used in other db's.

I want to change the name because (a) we are changing the semantics,
(b) we can't throw notices for opaque if we keep it as a valid choice.

>>> Maybe "anyarray" instead of "anyarraytype".
>> 
>> That would match with "any".

> I thought you wanted it separate ?

I meant that if the one name is "any", then making the other "anyarray"
(ie, both without "type" on the end) is consistent.
        regards, tom lane