| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
| Cc: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Get rid of system attributes in pg_attribute? |
| Date: | 2005-02-22 16:24:31 |
| Message-ID: | 10138.1109089471@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> writes:
> On Tuesday 22 February 2005 10:32, Tom Lane wrote:
>> Probably ctid is the more interesting case; I'm pretty sure ODBC relies
>> on ctid as a short-term-unique row identifier.
> Yeah... how many utility tools out there reference system columns explicitly?
> I think we need a scheme for allowing them to keep working even with user
> defined columns of the same name.
Well, that probably knocks out my thought that we could stop reserving
the system column names (at least ctid and xmin, which are the two that
actually seem useful to ordinary clients, need to stay reserved). But
it still seems like we don't have to represent these columns explicitly
in pg_attribute.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Darcy Buskermolen | 2005-02-22 16:57:30 | Re: psql: recall previous command? |
| Previous Message | Robert Treat | 2005-02-22 16:18:52 | Re: Get rid of system attributes in pg_attribute? |