Skip site navigation (1) Skip section navigation (2)


From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Fuhr <mike(at)fuhr(dot)org>
Cc: Kevin McArthur <postgresql-list(at)stormtide(dot)ca>,pgsql-hackers(at)postgresql(dot)org
Subject: Re: RESULT_OID Bug
Date: 2005-07-27 04:56:15
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Michael Fuhr <mike(at)fuhr(dot)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?


> 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

In response to


pgsql-hackers by date

Next:From: brookDate: 2005-07-27 05:17:57
Subject: Re: psql as an execve(2) interpreter
Previous:From: Tom LaneDate: 2005-07-27 04:41:26
Subject: Re: Duplicate object names in GRANT

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group