Re: cash_out bug

From: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>
To: "Alvaro Herrera" <alvherre(at)atentus(dot)com>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: cash_out bug
Date: 2002-08-12 04:47:38
Message-ID: GNELIHDDFBOCMGBFGEFOCEKECDAA.chriskl@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2002-08-12 04:54:09 Re: Interesting message about printf()'s in PostgreSQL
Previous Message Alvaro Herrera 2002-08-12 04:38:16 Re: cash_out bug