| From: | "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com> |
|---|---|
| To: | "Pedro Gimeno" <pgsql-001(at)personal(dot)formauri(dot)es> |
| Cc: | <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #3628: Wrong schema picked |
| Date: | 2007-09-24 09:23:20 |
| Message-ID: | 46F78208.7040805@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Pedro Gimeno wrote:
> When a function has a SQL statement to execute that has an unqualified
> table, that SQL statement doesn't always pick the table from a schema in the
> search_path.
The first time the function is run, all the statements in it are planned
and the schema used for the insert is resolved. Subsequent calls will
reuse the same plan. The obvious fix is to always explicitly specify the
schema in the INSERT. Or if if you want it to depend on the search_path,
you can execute it dynamically using EXECUTE
(http://www.postgresql.org/docs/8.2/static/plpgsql-statements.html#PLPGSQL-STATEMENTS-EXECUTING-DYN).
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Stark | 2007-09-24 12:00:06 | Re: Memory Allocation Error |
| Previous Message | Heikki Linnakangas | 2007-09-24 09:14:21 | Re: BUG #3627: Triple FK with ON DELETE SET NULL makes DELETE fail |