Re: Re: BUG #13685: Archiving while idle every archive_timeout with wal_level hot_standby

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: BUG #13685: Archiving while idle every archive_timeout with wal_level hot_standby
Date: 2016-02-23 13:31:00
Message-ID: CA+TgmobL1bT1snn3nMEZBRANfO-R4Vc55b14thRgwF4C+pCKXw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On Fri, Feb 19, 2016 at 6:32 AM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com> wrote:
>> To be honest, my heart still balances for the Extended() interface.
>> This reduces the risk of conflicts with back-patching with 9.5.
>
> Andres, others, what else can I do to make this thread move on? I can
> produce any version of this patch depending on committer's
> requirements.

FWIW, I don't expect to have time to review this in the level of
detail that would make me confident to commit it any time soon. I've
said my piece on what I think the final patch should look like, and I
hope that argument was persuasive, but I don't have anything further
to add to what I already said. I hope some other committer has some
cycles to look at this.

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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message ranier_gyn 2016-02-23 13:37:52 BUG #13980: UNINITIALIZED READ
Previous Message Francisco Olarte 2016-02-23 08:39:16 Re:

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2016-02-23 13:34:17 Re: [HACKERS] JDBC behaviour
Previous Message Robert Haas 2016-02-23 13:28:16 Re: Re: [COMMITTERS] pgsql: Add some isolation tests for deadlock detection and resolution.