Re: TODO: GRANT/REVOKE: Allow column-level privileges

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: kevin brintnall <kbrint(at)rufus(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: TODO: GRANT/REVOKE: Allow column-level privileges
Date: 2006-01-21 00:09:46
Message-ID: 6645.1137802186@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

kevin brintnall <kbrint(at)rufus(dot)net> writes:
> * add OID column to pg_attribute. This permits dependencies to be
> registered correctly in pg_shdepend.

No, no ... the precedent in pg_depend is that columns are represented as
the table's OID plus a column number. Please don't invent some random
other notation for a column, especially not one that is so expensive to
relate to the parent table. Add a subobject ID to pg_shdepend instead.

> STILL LEFT TO DO:

My recollection is that there's quite some deal of code that assumes
pg_attribute rows are fixed-width. You will have some issues there.
It's possible though that none of that code needs to access privileges,
in which case you'd be OK just dropping off the ACL data from the
in-memory copies of pg_attribute rows. Another possible solution is the
pg_attrdef model, ie, keep the ACLs somewhere else.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Rick Gigger 2006-01-21 00:18:28 Re: panic on 7.3
Previous Message kevin brintnall 2006-01-20 23:26:41 TODO: GRANT/REVOKE: Allow column-level privileges