Hi, Stephen Frost wrote: > As part of pg_attribute.. Having a seperate table would be an > alternative to adding a column to pg_shdepend.
Aha. Hm... I thought tracking dependencies between tables and attributes complicates DROP TABLE? Why doesn't that concern apply here? And why do we keep the attributes defaults in their own table with their own OID, instead of merging them into pg_attributes? (Or put another way around: why do these need their own dependency tracking, while the ACLs don't?) Or do we just want to keep the column-level privileges patch simple here and deferring other work to another patch? Regards Markus Wanner -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
