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

Поиск
Список
Период
Сортировка
От Zeugswetter Andreas SB SD
Тема Re: @(#) Mordred Labs advisory 0x0001: Buffer overflow in
Дата
Msg-id 46C15C39FEB2C44BA555E356FBCD6FA48879CF@m0114.s-mxs.net
обсуждение исходный текст
Ответы Re: @(#) Mordred Labs advisory 0x0001: Buffer overflow in
Список pgsql-hackers
> >> 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 increate function xx(any) returns text ...;

If that is possible, what is the difference to opaque ?

Andreas


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Bruce Momjian
Дата:
Сообщение: Re: @(#)Mordred Labs advisory 0x0003: Buffer overflow in
Следующее
От: Peter Eisentraut
Дата:
Сообщение: Re: CVS broken - large file support?