
> >> For that you would have to use "any", at the moment.  This would give
> >> you the same amount of type safety you have with "opaque", 
> ie, none.
> 
> > I would have to use some pg_proc magic to make "any" appear there,
> > since the plan was to not make it visible at the sql level, no ?
> 
> Huh?  It'll be perfectly visible.

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 ?

Andreas

Wed, 21 Aug 2002 19:18:46 +0200
"Zeugswetter Andreas SB SD" <ZeugswetterA@spardat.at>
Re: @(#) Mordred Labs advisory 0x0001: Buffer overflow in 
"Zeugswetter Andreas SB SD" <ZeugswetterA@spardat.at> writes:
> 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.

			regards, tom lane

Wed, 21 Aug 2002 13:31:01 -0400
Tom Lane <tgl@sss.pgh.pa.us>
Re: @(#) Mordred Labs advisory 0x0001: Buffer overflow in 