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

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org, Stephen Frost <sfrost(at)snowman(dot)net>
Subject: Re: Proposal: move column defaults into pg_attribute along with attacl
Date: 2008-09-21 17:39:44
Message-ID: 48D686E0.5080106@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:

>
> A possible objection to this plan is that if the column-level privileges
> patch doesn't get in, then we're left with a useless column in
> pg_attribute. But an always-null column doesn't cost much of anything,
> and we know that sooner or later we will support per-column ACLs:
> they are clearly useful as well as required by spec. So any
> inefficiency would only be transient anyway.

Right. I don't see this objection holding much water as column privs are
something that many in the community would like to see. If Stephen's
patch doesn't get in, it is likely it would (or a derivative there of)
within the 8.5 release cycle. If anything it just provides a stepping
stone. I see nothing wrong with that.

>
> Thoughts, objections?
>

+1

Sincerely,

Joshua D. Drake

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joe Conway 2008-09-21 17:58:29 Re: [patch] fix dblink security hole
Previous Message Naz 2008-09-21 17:25:35 pg_dump feature