Re: Logical decoding & exported base snapshot - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Logical decoding & exported base snapshot
Date
Msg-id CA+TgmoZ4SbxX0fWSaTZCQ3SH_L1DGxOazirGOge+7+z0x1gz8w@mail.gmail.com
Whole thread Raw
In response to Re: Logical decoding & exported base snapshot  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Thu, Dec 13, 2012 at 5:55 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> On Thu, Dec 13, 2012 at 5:25 PM, Andres Freund <andres@2ndquadrant.com> wrote:
>>> That would solve the consistency problem, yes. Would we need a special
>>> kind of permission for this? I would say superuser/database owner only?
>
>> Yeah, I doubt we would need a whole new permission for it, but it
>> would certainly have to be disallowed for ordinary users.
>
> Giving up the ability to run pg_dump as a non-superuser would be
> pretty annoying, so this would have to be an optional feature if we
> restrict it that way.

Yeah, for sure.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Logical decoding & exported base snapshot
Next
From: Robert Haas
Date:
Subject: Re: Use of systable_beginscan_ordered in event trigger patch