Skip site navigation (1) Skip section navigation (2)

Re: Get rid of system attributes in pg_attribute?

From: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>
To: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Get rid of system attributes in pg_attribute?
Date: 2005-02-22 13:29:47
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Monday 21 February 2005 04:23, Christopher Kings-Lynne wrote:
> > I'm wondering how useful it is to store explicit representations of the
> > system attributes in pg_attribute.  We could very easily hard-wire those
> > things instead, which would make for a large reduction in the number of
> > entries in pg_attribute.  (In the current regression database nearly
> > half of the rows have attnum < 0.)  I think the impact on the backend
> > would be pretty minimal, but I'm wondering if removing these entries
> > would be likely to break any client-side code.  Does anyone know of
> > client code that actually pays attention to pg_attribute rows with
> > negative attnums?
> Well, apart from a "attnum > 0" clause in phpPgAdmin, I don't think so...

Well, the corner case would be for those times when we use oid for updating 
specific rows in a table, if a user creates there own oid column then you 
could have trouble.   Actually we already have a safegaurd for this in 
phppgadmin so we wont cause mistakes, it's just that those updates probably 
won't work... others might not have been so thorough though. 

Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL

In response to


pgsql-hackers by date

Next:From: Hans-Jürgen SchönigDate: 2005-02-22 13:31:39
Subject: Question about "Unrecognized SPI code" ...
Previous:From: Teodor SigaevDate: 2005-02-22 10:32:09
Subject: int64/double for time/timestamp

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group