Re: Proposal: move column defaults into pg_attribute along with attacl - Mailing list pgsql-hackers

From Joshua D. Drake
Subject Re: Proposal: move column defaults into pg_attribute along with attacl
Date
Msg-id 48D686E0.5080106@commandprompt.com
Whole thread Raw
In response to Proposal: move column defaults into pg_attribute along with attacl  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Proposal: move column defaults into pg_attribute along with attacl  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Assert Levels
Next
From: Joe Conway
Date:
Subject: Re: [patch] fix dblink security hole