| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: cached plan issue in trigger func |
| Date: | 2009-03-25 17:13:32 |
| Message-ID: | 49CA663C.1080308@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>
>> I thought we had fixed this in 8.3:
>>
>
> I think that behavior is intentional: plancache.c can deal with the plan
> changing internally, but it doesn't expect that its callers could
> survive the plan's argument datatypes changing underneath them.
>
How do we reconcile that with this advertised feature of 8.3?:
* Automatically re-plan cached queries when table definitions change
or statistics are updated
How is a user to know when s/he can rely on this and when they can't? I
at least was expecting the plan to be invalidated by the table changes.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-03-25 17:25:01 | GIN versus zero-key queries |
| Previous Message | Guillaume Smet | 2009-03-25 17:07:24 | Re: display previous query string of idle-in-transaction |