| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Kouber Saparev <kouber(at)gmail(dot)com> |
| Cc: | Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BF mamba failure |
| Date: | 2026-07-07 23:59:35 |
| Message-ID: | ak2S5046X1aaagr4@paquier.xyz |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jul 07, 2026 at 01:13:59PM +0300, Kouber Saparev wrote:
> We had this issue again, the database just stopped - PostgreSQL 17.6.
>
> FATAL,XX000,"trying to drop stats entry already dropped: kind=relation
> dboid=16420 objoid=3885511363 refcount=1 generation=0"
>
> There is no such object present in the database.
>
> Do you think the issue might be fixed in PostgreSQL 18.4?... Or PostgreSQL
> 19 eventually?
Well, honestly, hard to say. That's a case where a reproducible
scenario would be useful, as it seems to ve very workload dependent in
terms of handling of the relation entries.. (Aka I have not dug in
details how to do that.)
As one example, the buildfarm seems to be quite silent, but it would
help if we need something like a wraparound for better
reproducibility.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2026-07-08 00:04:48 | Re: Fix unqualified catalog references in psql describe queries |
| Previous Message | Noah Misch | 2026-07-07 23:58:39 | Re: SPLIT/MERGE use of is_internal=true |