Re: pgsql: Implement backup API functions for non-exclusive backups

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-committers <pgsql-committers(at)postgresql(dot)org>
Subject: Re: pgsql: Implement backup API functions for non-exclusive backups
Date: 2016-04-06 16:41:46
Message-ID: CABUevEyFFR5mqttidNE7hq3JY_p3SkX6v0CPQ-GR+EVFmZYzLA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Wed, Apr 6, 2016 at 6:38 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Magnus Hagander <magnus(at)hagander(dot)net> writes:
> > Implement backup API functions for non-exclusive backups
>
> Shouldn't the CF entry for this be closed? The docs rewrite
> seems like a separate task.
>
>
It should. I forgot, thanks for the reminder. Done now.

--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Stephen Frost 2016-04-07 01:45:51 pgsql: Use GRANT system to manage access to sensitive functions
Previous Message Tom Lane 2016-04-06 16:38:48 Re: pgsql: Implement backup API functions for non-exclusive backups