| From: | Michael Paquier <michael(dot)paquier(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 04:48:47 |
| Message-ID: | CAB7nPqSYrmD=mZ3KUdKptmpd24t3=DxxS8-gUGh-CF_53_Z7yA@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:
> +1 for adding a new system attribute. We did something similar in
> Postgres-XC, though problem there was much simpler because we always
> knew that the remote FDW is a Postgres instance running the same
> version. So we added a new system column "node_id" which does not get
> any disk storage, but gets set during execution time depending on
> which node the tuple belongs to. The ctid system column of course is
> set to the remote ctid.
>
Just thinking aloud... This could also be merged in XC code and reduce XC
code footprint on PG core. <http://www.linkedin.com/in/pavandeolasee>
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2013-03-06 04:53:17 | Re: Parameterized paths vs index clauses extracted from OR clauses |
| Previous Message | Alvaro Herrera | 2013-03-06 04:39:16 | Re: sql_drop Event Trigger |