Re: cash_out bug - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject Re: cash_out bug
Date
Msg-id GNELIHDDFBOCMGBFGEFOCEKECDAA.chriskl@familyhealth.com.au
Whole thread Raw
In response to cash_out bug  (Alvaro Herrera <alvherre@atentus.com>)
Responses Re: cash_out bug  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> It turns out to be a far more serious bug than that, and is not limited
> to cash_out.  All these functions have the same problem:
>
> select proname from pg_proc where proargtypes=(select proargtypes from
> pg_proc where proname='cash_in') and pronargs=1 and proisstrict='t'
> order by proname;

Is this a problem in that the functions are definined to return opaque (eg.
PG_RETURN_VOID) but are then still usable in SELECT statements?

Chris



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: cash_out bug
Next
From: Tom Lane
Date:
Subject: Re: Interesting message about printf()'s in PostgreSQL