| From: | Markus Wanner <markus(dot)wanner(at)programmfabrik(dot)de> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stephen Frost <sfrost(at)snowman(dot)net>, "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-26 09:49:05 |
| Message-ID: | 48DCB011.7010206@programmfabrik.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera wrote:
> Tom Lane wrote:
>
>> I think adding a subobject column to pg_shdepend is probably the best
>> answer --- we only didn't do that to start with because we thought it
>> wasn't needed.
>
> Yep. I did consider adding it, but there was no use for it at the time
> so I just left it out. It's not like it's very difficult to add it at
> this point.
Sorry, I lost track here and would like to know the recommended course
of action for ACLs. I see these issues:
* make pg_attribute store VARLENA and/or NOT NULL fields
* dependency tracking of defaults (and ACLs)
* where to place ACLs (pg_attribute, merge with pg_attrdef or yet
another pg_attracl table)
So far I understood that merging pg_attrdef into pg_attribute is
unwanted due to complexity at DROP TABLE.
What does the subobject column for pg_shdepend buy us?
Clarification appreciated.
Regards
Markus Wanner
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2008-09-26 10:20:15 | Re: [PATCHES] Infrastructure changes for recovery |
| Previous Message | Stefan Kaltenbrunner | 2008-09-26 08:27:13 | Re: parallel pg_restore - WIP patch |