Re: Phantom Command ID - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: Phantom Command ID
Date
Msg-id 4519109A.60804@enterprisedb.com
Whole thread Raw
In response to Re: Phantom Command ID  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Phantom Command ID  ("Jim C. Nasby" <jim@nasby.net>)
List pgsql-hackers
Tom Lane wrote:
>> We could rename pg_attribute as pg_userattribute, and remove all the 
>> system attributes from that. To stay backwards-compatible, we could have 
>> a pg_attribute view on top of that contained the system attributes as well.
>>     
>
> I don't really think this is necessary.  How many client programs have
> you seen that don't explicitly exclude attnum<0 anyway?  The places that
> will need work are inside the backend, and a view won't help them.
>   

None, there probably isn't any client programs like that. It would be 
nice for programs to be able to discover what system attributes there 
is, though.

--  Heikki Linnakangas EnterpriseDB   http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Block B-Tree concept
Next
From: Bruce Momjian
Date:
Subject: Re: Release Notes: Major Changes in 8.2