| From: | "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Justin Clift" <justin(at)postgresql(dot)org>, "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>, "Vince Vielhaber" <vev(at)michvhf(dot)com>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: @(#) Mordred Labs advisory 0x0001: Buffer overflow in |
| Date: | 2002-08-21 16:10:48 |
| Message-ID: | 46C15C39FEB2C44BA555E356FBCD6FA4961E57@m0114.s-mxs.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > May be a plan could be to leave opaque, but throw a notice
> > when it is used in a create stmt, like:
> > NOTICE: the use of type OPAQUE should be avoided where possible
>
> Right, that's exactly the plan.
>
> Actually, I think we can tighten the use of OPAQUE quite a bit, too.
> The only supported uses will be (a) as an argument or result of a
> datatype's I/O function, (b) as the result of a trigger function.
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.
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-08-21 16:12:31 | Re: Dropping a schema |
| Previous Message | Thomas Lockhart | 2002-08-21 15:59:44 | Re: AT TIME ZONE bug in CVS? |