| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Adam Brightwell <adam(dot)brightwell(at)crunchydatasolutions(dot)com> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Petr Jelinek <petr(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Additional role attributes && superuser review |
| Date: | 2015-01-26 18:31:07 |
| Message-ID: | CA+TgmoZ4P6Hf7GO8w0=_ZB7f2UmTYYNBGQ28QhYNdOCSBZBQpA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jan 21, 2015 at 11:27 AM, Adam Brightwell
<adam(dot)brightwell(at)crunchydatasolutions(dot)com> wrote:
> After re-reading through this thread is seems like EXCLUSIVEBACKUP (proposed
> by Magnus) seemed to be a potentially acceptable alternative.
So this would let you do pg_start_backup() and pg_stop_backup(), but
it wouldn't let you run pg_basebackup against the server?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2015-01-26 18:34:34 | Re: Proposal: knowing detail of config files via SQL |
| Previous Message | Robert Haas | 2015-01-26 18:12:32 | Re: longjmp clobber warnings are utterly broken in modern gcc |