Re: Streaming replication as a separate permissions

Robert Haas <robertmhaas@gmail.com>

From: Robert Haas <robertmhaas@gmail.com>

To: Tom Lane <tgl@sss.pgh.pa.us>

Cc: Florian Pflug <fgp@phlo.org>, Magnus Hagander <magnus@hagander.net>, PostgreSQL-development <pgsql-hackers@postgresql.org>

Date: 2010-12-24T04:31:38Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Allow Win32 to compile under MinGW. Major changes are:
- 12c942383296 7.4.1 cited

On Thu, Dec 23, 2010 at 11:00 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Florian Pflug <fgp@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