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

From: Andres Freund <andres(at)anarazel(dot)de>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, bertranddrouvot(dot)pg(at)gmail(dot)com, florisvannee(at)optiver(dot)com, tgl(at)sss(dot)pgh(dot)pa(dot)us, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: error "can only drop stats once" brings down database
Date: 2024-06-07 03:12:58
Message-ID: 20240607031258.l4fcpvulo3uee5g6@awork3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 2024-06-07 11:46:04 +0900, Michael Paquier wrote:
> On Fri, Jun 07, 2024 at 10:15:40AM +0900, Kyotaro Horiguchi wrote:
> > To me, this is something that is not expected to happen, but if it
> > does, we would want detailed information. In that sense, it might be
> > better not to hide it in the DETAILS field.
>
> Same arguments here. A simple elog() makes easier to get to this
> data.

+1

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2024-06-07 07:55:29 BUG #18498: Locking a table from a trigger (with using two sessions) causes a deadlock: the bug or the feature?
Previous Message Michael Paquier 2024-06-07 02:46:04 Re: error "can only drop stats once" brings down database