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

From Tom Lane
Subject Re: @(#) Mordred Labs advisory 0x0001: Buffer overflow in
Date
Msg-id 6637.1029856418@sss.pgh.pa.us
Whole thread Raw
In response to Re: @(#) Mordred Labs advisory 0x0001: Buffer overflow  (Tatsuo Ishii <t-ishii@sra.co.jp>)
Responses Re: @(#) Mordred Labs advisory 0x0001: Buffer overflow  (Tatsuo Ishii <t-ishii@sra.co.jp>)
List pgsql-hackers
Tatsuo Ishii <t-ishii@sra.co.jp> writes:
>> Anyone see something I missed?  Tatsuo, what exactly should the function
>> signature really be for all those encoding conversion functions you just
>> added?

> test=# \df iso8859_1_to_utf8
>                                   List of functions
>  Result data type |   Schema   |       Name        |       Argument data types       
> ------------------+------------+-------------------+---------------------------------
>  integer          | pg_catalog | iso8859_1_to_utf8 | integer, integer, -, -, integer

Right, that's what they are now, but what do the "-" entries really
mean?  Also, are the "integer" args and result truthful, or do they
really mean something else?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: bison news
Next
From: "Nigel J. Andrews"
Date:
Subject: Re: @(#) Mordred Labs advisory 0x0001: Buffer overflow in