From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, Joachim Wieland <joe(at)mcknight(dot)de>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Logical decoding & exported base snapshot |
Date: | 2012-12-13 23:16:08 |
Message-ID: | CA+TgmoZ4SbxX0fWSaTZCQ3SH_L1DGxOazirGOge+7+z0x1gz8w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Dec 13, 2012 at 5:55 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> On Thu, Dec 13, 2012 at 5:25 PM, Andres Freund <andres(at)2ndquadrant(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2012-12-13 23:18:45 | Re: Use of systable_beginscan_ordered in event trigger patch |
Previous Message | Tom Lane | 2012-12-13 22:55:18 | Re: Logical decoding & exported base snapshot |