| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Sorting out acl fixes |
| Date: | 2004-07-22 04:21:49 |
| Message-ID: | 40FF40DD.4030502@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> When did that get to be part of the requirements? I don't even know
> who you expect to do this (backend? pg_dump? user?) or at what level
> you think the fixing should happen (GRANT/REVOKE? UPDATE pg_class
> SET relacl = fixme(relacl)? direct hacking of the ACL array?). To
> say nothing of the semantic problems of deciding what an invalid
> ACL is really supposed to mean.
I was referring to fixing my own database that is full of these acls
that dump incorrectly - perhaps you don't give me enough credit. I'm
thinking that if I can find a watertight way of fixing it at pg_dump
time I should, for pre 7.5 databases. Should I?
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | K-Sudhakaran | 2004-07-22 04:31:10 | Hi ...Inheritance in postgres 7.3.4 reg. |
| Previous Message | Tom Lane | 2004-07-22 03:57:40 | Re: Sorting out acl fixes |