From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Florian Pflug <fgp(at)phlo(dot)org> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Thom Brown <thom(at)linux(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: FDW system columns |
Date: | 2011-11-14 02:25:15 |
Message-ID: | CA+Tgmoao2wDwLq9mBOU2MEum3qD2U0aiu28fd7p7-M3JVk8iOQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, Nov 13, 2011 at 6:57 PM, Florian Pflug <fgp(at)phlo(dot)org> wrote:
> 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)
My vote is to nuke 'em all. :-)
I don't think that we want to encourage people to depend on the
existence of system columns any more than they do already.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2011-11-14 02:35:28 | psql history vs. dearmor (pgcrypto) |
Previous Message | Robert Haas | 2011-11-14 01:57:17 | Re: why do we need two snapshots per query? |