| From: | Florian Pflug <fgp(at)phlo(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Thom Brown <thom(at)linux(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: FDW system columns |
| Date: | 2011-11-13 23:57:42 |
| Message-ID: | BB3D33F5-156C-4588-819A-B434693155CF@phlo.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Nov13, 2011, at 01:38 , Tom Lane wrote:
> Just a couple hours ago I was wondering why we create system columns for
> foreign tables at all. Is there a reasonable prospect that they'll ever
> be useful? I can see potential value in tableoid, but the others seem
> pretty dubious --- even if you were fetching from a remote PG server,
> the XIDs would not be meaningful within our own environment.
At least ctid seems useful too. I've used that in the past as a poor man's
surrogate primary key.
Also, people have used ctid and xmin in the past to re-find previously
visited rows and to check whether they've been modified. So there might be
some value in keeping xmin around also (and make the postgres fdw populate it)
best regards,
Florian Pflug
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-11-14 00:37:29 | Re: why do we need two snapshots per query? |
| Previous Message | Florian Pflug | 2011-11-13 23:45:04 | Re: why do we need two snapshots per query? |