<p dir="ltr"><br /> On Oct 16, 2014 1:59 PM, "Stephen Frost" <<a
href="mailto:sfrost@snowman.net">sfrost@snowman.net</a>>wrote:<br /> ><br /> > * Simon Riggs
(simon@2ndQuadrant.com)wrote:<br /> > > On 15 October 2014 06:22, Stephen Frost <<a
href="mailto:sfrost@snowman.net">sfrost@snowman.net</a>>wrote:<br /> > > > BACKUP:<br /> > > >
pg_start_backup()<br /> > > > pg_stop_backup()<br /> > > > pg_switch_xlog()<br /> > >
> pg_create_restore_point()<br /> > ><br /> > > Yes, but its more complex. As Jim says, you need to
includepg_dump,<br /> > > plus you need to include the streaming utilities, e.g. pg_basebackup.<br /> ><br />
>I'd rather have more, simpler, role attributes than one 'catch-all'.<br /> ><br /> > Once I understand what
"includepg_dump" and "include pg_basebackup"<br /> > mean, I'd be happy to work on adding those.<br /> ><p
dir="ltr">Includepg_basebackup would mean the replication protocol methods for base backup and streaming. Which is
alreadycovered by the REPLICATION flag. <p dir="ltr">But in think it's somewhat useful to separate these. Being able to
executepg_stop_backup allows you to break somebody else's backup currently running, which pg_basebackup is safe
against.So being able to call those functions is clearly a higher privilege than being able to use pg_basebackup. <p
dir="ltr">/Magnus