| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
| Cc: | florisvannee(at)optiver(dot)com, andres(at)anarazel(dot)de, bertranddrouvot(dot)pg(at)gmail(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-16 23:28:10 |
| Message-ID: | Zm91CpHheqXC_S_V@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2024-06-16 23:30:46 | Re: BUG #18499: Reindexing spgist index concurrently triggers Assert("TransactionIdIsValid(state->myXid)") |
| Previous Message | Michael Paquier | 2024-06-16 23:24:10 | Re: BUG #18499: Reindexing spgist index concurrently triggers Assert("TransactionIdIsValid(state->myXid)") |