| From: | Andrea Lombardoni <andrea(at)lombardoni(dot)ch> |
|---|---|
| To: | adrian(dot)klaver(at)gmail(dot)com |
| Cc: | pgsql-general(at)postgresql(dot)org, "A(dot) Kretschmer" <andreas(dot)kretschmer(at)schollglas(dot)com> |
| Subject: | Re: Problem with temporary tables |
| Date: | 2010-06-30 13:41:18 |
| Message-ID: | AANLkTikiMqbctuDHRL0deLbrqNTi765ElD-B9xEedxW4@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> You need to use EXECUTE for the INSERT statement as well per error:
>
> CONTEXT: SQL statement "INSERT INTO idmap (oldid, type, newid) VALUES(1,
> 1, 1)" PL/pgSQL function "test" line 16 at SQL statement
Thanks, this works and solves my problem.
Still, I find this behaviour to be rather quirky.
Ideally the generated query plan should notice such cases and either
report an error or use the version of the temporary table currently
'live'.
At least this quirk should be highlighted both in the plpgsql
documentation page
http://www.postgresql.org/docs/8.2/interactive/plpgsql-overview.html
and linked from the CREATE TABLE page
http://www.postgresql.org/docs/8.2/interactive/sql-createtable.html
I will propose these changes in the appropriate mailing lists.
Have a nice day!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Grzegorz Jaśkiewicz | 2010-06-30 13:46:53 | Re: Problem with temporary tables |
| Previous Message | Adrian Klaver | 2010-06-30 13:27:50 | Re: Problem with temporary tables |