| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Frank van Vugt <ftm(dot)van(dot)vugt(at)foxi(dot)nl>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: SPI_ERROR_CONNECT within pl/pgsql, PG 8.4 |
| Date: | 2009-07-14 16:54:17 |
| Message-ID: | 25339.1247590457@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alan Pinstein | 2009-07-15 04:54:00 | BUG #4921: ltree @> ltree[] operator shouldn't fail if ltree[] is empty |
| Previous Message | Tom Lane | 2009-07-14 16:51:33 | Re: SPI_ERROR_CONNECT within pl/pgsql, PG 8.4 |