Re: AW: pg_attribute growing and growing and growing - Mailing list pgsql-hackers

From Tom Lane
Subject Re: AW: pg_attribute growing and growing and growing
Date
Msg-id 1618.966867817@sss.pgh.pa.us
Whole thread Raw
In response to AW: pg_attribute growing and growing and growing  (Zeugswetter Andreas SB <ZeugswetterA@wien.spardat.at>)
List pgsql-hackers
Zeugswetter Andreas SB <ZeugswetterA@wien.spardat.at> writes:
>> Since table OIDs keep increasing, this formulation ensures that new
>> entries will always sort to the end of the index, and so space freed
>> internally in the indexes can never get re-used.  Swapping the column
>> order may eliminate that problem --- but I'm not sure what if any
>> speed penalty would be incurred.  Thoughts anyone?

> Isn't pg_attribute often accessed with a "where oid=xxx" restriction
> to get all cols for a given table ?

Hmm, good point.  I don't think the system itself does that --- AFAIR
it just looks up specific rows by relid+name or relid+num --- but making
this change would make the indexes useless for applications that make
that kind of query.

Oh well, back to the drawing board...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tiago Antão
Date:
Subject: Re: Optimisation deficiency: currval('seq')-->seq scan, constant-->index scan
Next
From: Don Baccus
Date:
Subject: Re: Optimisation deficiency: currval('seq')-->seq scan, constant-->index scan