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 24860.1029946721@sss.pgh.pa.us
Whole thread Raw
In response to Re: @(#) Mordred Labs advisory 0x0001: Buffer overflow in  ("Zeugswetter Andreas SB SD" <ZeugswetterA@spardat.at>)
List pgsql-hackers
"Zeugswetter Andreas SB SD" <ZeugswetterA@spardat.at> writes:
> In my paper I use C functions that take "any tuple".
> I do not yet see how I can do that without opaque if we don't 
> have a "row" but only a "trigger" type.

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.

We could talk about adding more pseudotypes that are geared to
requirements not existing in the standard set of functions ...
but I'm going to concentrate on those first.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Neil Conway
Date:
Subject: Re: @(#)Mordred Labs advisory 0x0002: Buffer overflow in PostgreSQL
Next
From: Bruce Momjian
Date:
Subject: Re: @(#)Mordred Labs advisory 0x0003: Buffer overflow in