From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Jaimin Pan <jaimin(dot)pan(at)gmail(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Error of insert Foreign table with postgres_fdw |
Date: | 2017-08-07 13:19:26 |
Message-ID: | 20776.1502111966@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Jaimin Pan <jaimin(dot)pan(at)gmail(dot)com> writes:
> I got error when insert a parent table by inserting a foreign table.
> ...
> (create trigger "phone_pool_insert_trigger" for phone_pool and insert into
> phone_pool works well. The child table got the row.)
> when insert into phone_pool_foreign. I got error like following.
> ERROR: relation "ph_90" does not exist
> CONTEXT: Remote SQL command: INSERT INTO public. phone_pool_foreign(id,
> patrition, phone, carrier, createtime, updatetime, deleteflg) VALUES ($1,
> $2, $3, $4, $5, $6, $7)
> PL/pgSQL function public.phone_pool_insert_trigger() line 93 at SQL
> statement
> """
You didn't show us either the whole trigger or the failing statement in
it, but I bet you forgot to schema-qualify the child table names.
postgres_fdw runs the remote session with a very restrictive search_path,
just pg_catalog if memory serves. It's generally bad practice for
triggers to rely on the prevailing search path in any case.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Verite | 2017-08-07 13:52:33 | Re: Crash report for some ICU-52 (debian8) COLLATE and work_mem values |
Previous Message | Euler Taveira | 2017-08-07 13:03:20 | Re: BUG #14771: "Logical decoding" does not cover the impact of "TRUNCATE TABLE" command |