From: Floris Van Nee <florisvannee@Optiver.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Andres Freund <andres@anarazel.de>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Subject: RE: error "can only drop stats once" brings down database
Date: Wed, 5 Jun 2024 10:31:04 +0000
Message-ID: <68430b1b76d44558b7b07ae8c69151f6@Optiver.com> (raw)
In-Reply-To: <Zl6gQNSeWoBdijxZ@paquier.xyz>
References: <b14ae28029f64757bb64613be2549a74@Optiver.com>
<215498.1708454947@sss.pgh.pa.us>
<8e5cb534706a4f43bd74405c8fd91437@Optiver.com>
<20240505160915.6boysum4f34siqct@awork3.anarazel.de>
<20240505223546.6yvjzgqifuoiii3e@awork3.anarazel.de>
<47ca6fcc687e408287871f7eaaaf3c3b@Optiver.com>
<Zl6gQNSeWoBdijxZ@paquier.xyz>
>
> The only reason why I did not do one or the other yet is that this is an
> improvement, hence I was waiting for v18 to open. If somebody feels
> differently, feel free to proceed before that with the format you like. Still I'd
> vote for the addition of the refcount to the patch proposed on this thread, to
> provide more debugging info to the information reported.
This patch would help in getting more info about this specific issue if it reoccurs, but in that case it's only helpful if it's backpatched.
Agree the refcount addition makes sense.
-Floris
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: florisvannee@Optiver.com, michael@paquier.xyz, andres@anarazel.de, tgl@sss.pgh.pa.us, pgsql-bugs@lists.postgresql.org
Subject: RE: error "can only drop stats once" brings down database
In-Reply-To: <68430b1b76d44558b7b07ae8c69151f6@Optiver.com>
* 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