Re: PATCH: Make pg_stop_backup() archive wait optional

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: David Steele <david(at)pgmasters(dot)net>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PATCH: Make pg_stop_backup() archive wait optional
Date: 2017-03-06 18:07:06
Message-ID: CA+TgmoZfLBR5V-v_C9hPqgh2=sFLnOy+nCsL6kVLY8AdL9s4-A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Mar 6, 2017 at 12:53 PM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> Regarding 02, I certainly see that as valuable for the reasons which
> David outlined in his initial email. I can certainly take point on
> getting it committed, but I wouldn't complain if someone else does
> either.

Sold, to the snowman in the first row.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Corey Huinker 2017-03-06 18:10:49 Re: contrib modules and relkind check
Previous Message Robert Haas 2017-03-06 18:05:44 Re: PATCH: two slab-like memory allocators