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

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: l(at)lrowe(dot)co(dot)uk
Cc: PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, Robert Haas <robertmhaas(at)gmail(dot)com>
Subject: Re: BUG #13685: Archiving while idle every archive_timeout with wal_level hot_standby
Date: 2015-10-20 00:21:38
Message-ID: CAB7nPqSy9VD21mmBA_pG3c6WAgAfheb0VFWzx7d6gYhZmgtgvQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On Sat, Oct 17, 2015 at 11:10 PM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com>wrote:

> I think that a simple idea would be to not call LogStandbySnapshot() when
> we are still at the beginning of a new segment. We know that the first page
> of a WAL segment has a size of SizeOfXLogLongPHD, so just having a check on
> that sounds enough to me. Per se the patch attached that should be applied
> down to 9.4. This fixes the regression reported by Laurence for me.
>

This bug fix is registered in next CF so as we do not lose track of it;
https://commitfest.postgresql.org/7/398/
--
Michael

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2015-10-20 02:07:00 Re: database and table information collect
Previous Message 許耀彰 2015-10-19 23:07:32 database and table information collect

Browse pgsql-hackers by date

  From Date Subject
Next Message Kouhei Kaigai 2015-10-20 00:36:24 Re: Foreign join pushdown vs EvalPlanQual
Previous Message Tomas Vondra 2015-10-20 00:16:03 Re: Multi-column distinctness.