Re: Proposal: move column defaults into pg_attribute along with attacl

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Markus Wanner <markus(at)bluegap(dot)ch>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Proposal: move column defaults into pg_attribute along with attacl
Date: 2008-09-23 13:55:35
Message-ID: 20080923135535.GE16005@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom,

* Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
> Markus Wanner <markus(at)bluegap(dot)ch> writes:
> > ISTM that we should at least combine defaults and ACLs then, as proposed
> > by Stephen.
>
> Huh? Maybe I missed something, but I didn't think that was suggested
> anywhere.

I had suggested a single table, with an OID, which would house anything
that needed a seperate OID for columns (defaults and ACLs currently) in
20080922024129(dot)GD16005(at)tamriel(dot)snowman(dot)net(dot) It's not a completely
thought-through solution, just something that struck me as a more
general way of handling these situations (assuming we have more in the
future and don't want to give each one its own table). If putting them
together implies we have to complicate things to add some way to
seperate them then it might not be worth it. Having a seperate table
for each means we can use the table's OID to seperate them though. I
still dislike this possible continued growth of the catalogs.

Thanks,

Stephen

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-09-23 13:56:33 Re: pg_type.h regression?
Previous Message Tom Lane 2008-09-23 13:49:57 Re: Initial prefetch performance testing