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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Kyotaro Horiguchi <horikyota(dot)ntt(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 09:49:16
Message-ID: ZmLXnAtRSUudsFqg@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Jun 07, 2024 at 09:32:13AM +0000, Bertrand Drouvot wrote:
> That was a nit, so fine by me to move on with a simple elog().

Okay, I've just applied the elog() version down to 15 then. Now,
about the entry getting dropped twice..
--
Michael

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2024-06-07 11:00:00 BUG #18499: Reindexing spgist index concurrently triggers Assert("TransactionIdIsValid(state->myXid)")
Previous Message Dmitry Koval 2024-06-07 09:45:26 Re: BUG #18498: Locking a table from a trigger (with using two sessions) causes a deadlock: the bug or the feature?