From: Michael Paquier <michael@paquier.xyz>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Dmitry Dolgov <9erthalion6@gmail.com>
Cc: Alexander Kukushkin <cyberdemn@gmail.com>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #15346: Replica fails to start after the crash
Date: Thu, 23 Aug 2018 13:14:20 +0900
Message-ID: <20180823041420.GA1158@paquier.xyz> (raw)
In-Reply-To: <20180822175034.lnvwk5js32k6mjyz@alvherre.pgsql>
References: <CA+q6zcVjv1Lp-3=prBbpq2CbBioK91SHarfw3F8FHuUN4EwcUA@mail.gmail.com>
<20180822175034.lnvwk5js32k6mjyz@alvherre.pgsql>
On Wed, Aug 22, 2018 at 02:50:34PM -0300, Alvaro Herrera wrote:
> On 2018-Aug-22, Dmitry Dolgov wrote:
> I don't know. I was thinking it could detect some invalid write in
> shared memory.
invalid_page_tab does not use HASH_SHARED_MEM. What did you have in
mind?
On my side, I have been letting a primary/standby set run for a certain
amount of time with the following running:
- pgbench load on the primary.
- background worker connecting to database, just running in loop and
sleeping. It uses BgWorkerStart_ConsistentState as start mode.
- The standby gets stopped in immediate mode, and restarted after some
time to let some activity happening after the recovery point has been
reached.
After close to an hour of repeated tests, I am not able to reproduce
that. Maybe there are some specifics in your schema causing more
certain types of records to be created. Could you check if in the set
of WAL segments replayed you have references to the block the hash table
is complaining about?
--
Michael
Attachments:
signature.asc (application/pgp-signature, 832B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: michael@paquier.xyz, alvherre@2ndquadrant.com, 9erthalion6@gmail.com, cyberdemn@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #15346: Replica fails to start after the crash
In-Reply-To: <20180823041420.GA1158@paquier.xyz>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox