Re: RESULT_OID Bug - Mailing list pgsql-hackers

From Tom Lane
Subject Re: RESULT_OID Bug
Date
Msg-id 21868.1122440175@sss.pgh.pa.us
Whole thread Raw
In response to Re: RESULT_OID Bug  (Michael Fuhr <mike@fuhr.org>)
Responses Re: RESULT_OID Bug  (Michael Fuhr <mike@fuhr.org>)
List pgsql-hackers
Michael Fuhr <mike@fuhr.org> writes:
> On Wed, Jul 27, 2005 at 12:08:18AM -0400, Tom Lane wrote:
>> I tried to reproduce the problem ... no joy ...

> Hmmm...not even with the example that starts from initdb?

Nope...

> Could this be platform-specific?

Seems that way.  I tried it on HPUX 10.20/HPPA/gcc 2.95.3.

My guess is that the behavior is related to plpgsql's caching
of plans for functions, and as such should be driven by the
backend's history not the whole database's history.  But it's
just a guess.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Duplicate object names in GRANT
Next
From:
Date:
Subject: Re: psql as an execve(2) interpreter