| From: | "Brendan Jurd" <direvus(at)gmail(dot)com> |
|---|---|
| To: | "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: plpgsql: Plan type mismatch error |
| Date: | 2007-10-16 05:30:46 |
| Message-ID: | 37ed240d0710152230n715c31d8j9d6b1901a1ba611f@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 10/16/07, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
> please, read:
> http://www.pgsql.cz/index.php/Automatic_execution_plan_caching_in_PL/pgSQL
>
Thanks Pavel,
I actually came across that wiki article via Google when I was first
trying to learn more about the message. But, I'm not asking for help
understanding how plan caching works. As mentioned, I've already
fixed the problem with my function.
Rather, I'm suggesting that we increase the helpfulness of the error message.
BJ
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jacky Leng | 2007-10-16 10:30:10 | Why copy_relation_data only use wal when WAL archiving is enabled |
| Previous Message | Pavel Stehule | 2007-10-16 05:15:20 | Re: plpgsql: Plan type mismatch error |