| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Weird pg_dumpall bug? |
| Date: | 2006-01-24 15:04:30 |
| Message-ID: | 1138115070.3177.3.camel@swithin |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 2006-01-24 at 09:44 -0500, Stephen Frost wrote:
> * Christopher Kings-Lynne (chriskl(at)familyhealth(dot)com(dot)au) wrote:
> > Hmmmm...actually. It's because I have a user called 'support' and a
> > group called 'support'.
> >
> > Seems like it needs a fix...
>
> Have you got a suggestion on just how to fix it...? Debian's
> pg_upgradecluster bails out with an error when it discovers this
> situation but I don't think it'd be sensible for pg_dump to do that...
>
How about an option to map groups whose names conflict with user names
using a prefix mechanism?
e.g. --map-conflicting-groups=gr_
Then in Christopher's example his support group would become the role
gr_support.
Just a thought.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-01-24 15:05:43 | Re: Weird pg_dumpall bug? |
| Previous Message | Stephen Frost | 2006-01-24 14:44:55 | Re: Weird pg_dumpall bug? |