On Thu, Dec 23, 2010 at 11:00 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Florian Pflug <f...@phlo.org> writes: >> The problem here is that you suggest NOLOGIN should mean "Not allowed >> to issue SQL commands", which really isn't what the name "NOLOGIN" >> conveys. > > No, it means "not allowed to connect". It's possible now to issue > commands as a NOLOGIN user, you just have to use SET ROLE to become the > user. I think you're arguing about a design choice that was already > made some time ago.
I think I agree with Florian about the confusing-ness of the proposed semantics. Aren't you saying you want NOLOGIN mean "not allowed to log in for the purposes of issuing SQL commands, but allowed to log in for replication"? Uggh. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
