Re: error "can only drop stats once" brings down database

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Floris Van Nee <florisvannee(at)optiver(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>
Subject: Re: error "can only drop stats once" brings down database
Date: 2024-06-06 04:44:26
Message-ID: ZmE-qm8d9kfDfnMy@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Jun 05, 2024 at 10:31:04AM +0000, Floris Van Nee wrote:
> 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.

Adding Bertrand in CC as he was similarly playing with this area.

What would both of you think about the attached. This is a mix of
what's been proposed on the two threads, with the addition of the
refcount.
--
Michael

Attachment Content-Type Size
pgstat-drop-debug.patch text/x-diff 748 bytes

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message David Rowley 2024-06-06 05:04:36 Re: BUG #18477: A specific SQL query with "ORDER BY ... NULLS FIRST" is performing poorly if an ordering column is n
Previous Message Tom Lane 2024-06-06 03:48:09 Re: BUG #18477: A specific SQL query with "ORDER BY ... NULLS FIRST" is performing poorly if an ordering column is n