| From: | Shigeru Hanada <shigeru(dot)hanada(at)gmail(dot)com> |
|---|---|
| To: | Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Writable foreign tables: how to identify rows |
| Date: | 2013-03-06 10:42:23 |
| Message-ID: | CAEZqfEdWjd1oOyDjPuEZOU6k4Baf_=Fwm5g_Vp+FKpPBc57Opg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Mar 6, 2013 at 12:35 PM, Pavan Deolasee
<pavan(dot)deolasee(at)gmail(dot)com> wrote:
> In the context of postgres_fdw, I am not sure if we need an additional
> system column like a node_id. Would there be a possibility where
> tuples to-be-modified are coming from different foreign tables and at
> runtime we need to decide where to execute the UPDATE/DELETE operation
> ? If we start supporting inheritance involving foreign tables as child
> tables, this will become a reality.
Foreign tables have tableoid system column which holds pg_class.oid of
the foreign table. It seems sufficient to determine source server.
--
Shigeru HANADA
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bernd Helmle | 2013-03-06 11:00:33 | Materialized View patch broke pg_dump |
| Previous Message | Albe Laurenz | 2013-03-06 10:04:25 | Re: [GENERAL] Floating point error |