Re: @(#) Mordred Labs advisory 0x0001: Buffer overflow in - Mailing list pgsql-hackers

From Zeugswetter Andreas SB SD
Subject Re: @(#) Mordred Labs advisory 0x0001: Buffer overflow in
Date
Msg-id 46C15C39FEB2C44BA555E356FBCD6FA4961E5A@m0114.s-mxs.net
Whole thread Raw
Responses Re: @(#) Mordred Labs advisory 0x0001: Buffer overflow in  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> > I did not mean visible, I meant useable, like in
> >     create function xx(any) returns text ...;
> > If that is possible, what is the difference to opaque ?
>
> "any" will have the same behavior that "opaque" used to have, yes.

Ok, now I vote, that you don't implement "any" and use "opaque".
I don't think we want two types that do the same thing.
Is it that you like the name "any" more than "opaque" ?
I am confused.

Andreas


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: @(#) Mordred Labs advisory 0x0001: Buffer overflow in
Next
From: Neil Conway
Date:
Subject: Re: @(#)Mordred Labs advisory 0x0002: Buffer overflow in PostgreSQL