From: Michael Paquier <michael@paquier.xyz>
To: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: florisvannee@optiver.com
Cc: andres@anarazel.de
Cc: bertranddrouvot.pg@gmail.com
Cc: tgl@sss.pgh.pa.us
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: error "can only drop stats once" brings down database
Date: Mon, 17 Jun 2024 08:28:10 +0900
Message-ID: <Zm91CpHheqXC_S_V@paquier.xyz> (raw)
In-Reply-To: <ZmuQz8IN6MpLxKs8@paquier.xyz>
References: <2cb577e176774caca28c724898768a38@Optiver.com>
<ZmafJO3lpMjbyHXv@paquier.xyz>
<e6a0bc8861b64acabce57c88e8e2c029@Optiver.com>
<20240611.164457.1388765109177375375.horikyota.ntt@gmail.com>
<ZmuQz8IN6MpLxKs8@paquier.xyz>
On Fri, Jun 14, 2024 at 09:37:35AM +0900, Michael Paquier wrote:
> I am wondering if we should tackle this problem by adding a notion of
> "age" in the stats entries for what's stored in the central dshash and
> in the hold copies in the backends, so as we dump the "age" of an
> existing stats entry if we find out that it gets reused in a create
> path. That requires some design and would not be backpatchable, but
> it does not seem that invasive at quick glance (I had my eyes on this
> code the full week). Other thoughts are welcome.
This still sounds like a good idea after sleeping on it over the
weekend. Please note that I am moving on with the problem on this
thread where this has been reported, and that is the point of origin:
https://www.postgresql.org/message-id/ZmvVudpT8z6hbY9t@paquier.xyz
Let's continue the discussion there.
--
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, horikyota.ntt@gmail.com, florisvannee@optiver.com, andres@anarazel.de, bertranddrouvot.pg@gmail.com, tgl@sss.pgh.pa.us, pgsql-bugs@lists.postgresql.org
Subject: Re: error "can only drop stats once" brings down database
In-Reply-To: <Zm91CpHheqXC_S_V@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