From: | Aidan Van Dyk <aidan(at)highrise(dot)ca> |
---|---|
To: | Jaime Casanova <jaime(at)2ndquadrant(dot)com> |
Cc: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Hannu Krosing <hannu(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: What Would You Like To Do? |
Date: | 2011-09-14 16:49:01 |
Message-ID: | CAC_2qU_XzJZTcTUEiWBa3Fusr2+nAVeYXaN5NkLKnV7NVSYPUA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Sep 14, 2011 at 12:09 PM, Jaime Casanova <jaime(at)2ndquadrant(dot)com> wrote:
> last time i tried it (last year), it seems broken because i couldn't
> log in with any user anymore... but it could be that i did something
> wrong so i didn't report until i could confirm but i hadn't the time
> and i forgot it since then
I haven't tried it on 9.0/9.1, but I used it on a 8.4 cluster, and "it
worked", with all the caveats of needing all the user(at)database users
created correctly, and the right use of quoting, and @ in logins,
etc.... The biggest being the lack of md5...
Definitely not "straight forward", and users are still "global", just
suffixed with an "@database" to make then "unique" between database
namespaces.
But I found it useful when needing to hand out "seperate" usernames
for different apps because they all needed to have their own
search_path and other settings set before login (yes, dumb apps,
mostly odbc), and be able to have the same "userid" for different
databases, using different settings...
a.
--
Aidan Van Dyk Create like a god,
aidan(at)highrise(dot)ca command like a king,
http://www.highrise.ca/ work like a slave.
From | Date | Subject | |
---|---|---|---|
Next Message | Jaime Casanova | 2011-09-14 17:01:57 | Re: What Would You Like To Do? |
Previous Message | Jaime Casanova | 2011-09-14 16:09:26 | Re: What Would You Like To Do? |