Re: SPI_ERROR_CONNECT within pl/pgsql, PG 8.4 - Mailing list pgsql-bugs

From Tom Lane
Subject Re: SPI_ERROR_CONNECT within pl/pgsql, PG 8.4
Date
Msg-id 25339.1247590457@sss.pgh.pa.us
Whole thread Raw
In response to Re: SPI_ERROR_CONNECT within pl/pgsql, PG 8.4  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: SPI_ERROR_CONNECT within pl/pgsql, PG 8.4
List pgsql-bugs
Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes:
> Tom Lane wrote:
>> [ looks at CVS logs ... ]  Another case that will cause plan
>> invalidation in 8.4 and not 8.3 is creating or dropping a schema.
>> Do you do a lot of that?

> Hmm, he says he uses temporary tables. Does creating/dropping a
> temporary namespace trigger plan cache invalidation?

It could, but I suppose that most DBs would soon reach a steady state
where they have all the pg_temp_ schemas they need.  (Hadn't occurred to
me before, but this is a real good reason for the implementation not
discarding the actual schema when a temp namespace is recycled ...)

            regards, tom lane

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: SPI_ERROR_CONNECT within pl/pgsql, PG 8.4
Next
From: "Sergey Konoplev"
Date:
Subject: BUG #4922: Segmentation fault on high-loaded server (+coredump backtrace)