Re: Updated backup APIs for non-exclusive backups

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: David Steele <david(at)pgmasters(dot)net>, Marco Nenciarini <marco(dot)nenciarini(at)2ndquadrant(dot)it>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>
Subject: Re: Updated backup APIs for non-exclusive backups
Date: 2016-04-01 03:09:47
Message-ID: CAA4eK1+Jqt8Lpad=JDn6YmU32i1TGDQ+yE4ro87ARGVF07fGCw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Mar 31, 2016 at 5:49 PM, Magnus Hagander <magnus(at)hagander(dot)net>
wrote:

> On Thu, Mar 31, 2016 at 4:00 AM, David Steele <david(at)pgmasters(dot)net> wrote:
> So maybe we should at least start that way. And just document that
> clearly, and then use the patch that we have right now?
>
> Except we add so it still returns the stoppoint() as well (which is
> returned from the current pg_stop_backup, but not in the new one).
>
> We can always extend the function with more columns later if we need -
> it's changing the ones we have that's a big problem there :)
>
>
+1 for doing that way for now.

With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Petr Jelinek 2016-04-01 03:13:41 Re: Re: [COMMITTERS] pgsql: Enable logical slots to follow timeline switches
Previous Message Thomas Munro 2016-04-01 02:57:46 Re: So, can we stop supporting Windows native now?