From: Michael Paquier <michael@paquier.xyz>
To: Fujii Masao <masao.fujii@oss.nttdata.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: ERROR: invalid spinlock number: 0
Date: Thu, 11 Feb 2021 21:55:40 +0900
Message-ID: <YCUpTL8bZHa+9K+0@paquier.xyz> (raw)
In-Reply-To: <7ef8708c-5b6b-edd3-2cf2-7783f1c7c175@oss.nttdata.com>
References: <7ef8708c-5b6b-edd3-2cf2-7783f1c7c175@oss.nttdata.com>
Hi Fujii-san,
On Tue, Feb 09, 2021 at 11:17:04PM +0900, Fujii Masao wrote:
> ISTM that the commit 2c8dd05d6c caused this issue. The commit changed
> pg_stat_get_wal_receiver() so that it reads "writtenUpto" by using
> pg_atomic_read_u64(). But since "writtenUpto" is initialized only when
> walreceiver starts up, reading "writtenUpto" before the startup of
> walreceiver can cause the error.
Indeed, that's a problem. We should at least move that out of the
spin lock area. I'll try to look at that in details, and that's going
to take me a couple of days at least. Sorry for the delay.
--
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-hackers@postgresql.org
Cc: michael@paquier.xyz, masao.fujii@oss.nttdata.com
Subject: Re: ERROR: invalid spinlock number: 0
In-Reply-To: <YCUpTL8bZHa+9K+0@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