| From: | Anthonin Bonnefoy <anthonin(dot)bonnefoy(at)datadoghq(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, David Rowley <dgrowleyml(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Xact end leaves CurrentMemoryContext = TopMemoryContext |
| Date: | 2025-03-10 08:41:56 |
| Message-ID: | CAO6_XqrCwT0e5VdY8V2_GHPOB26_omURuWoPTNA1dxB=JLNnaQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
This change seems to have introduced an issue where a deleted context
can be restored. This happens when a replication command exports a
snapshot since the transaction used is aborted at the start of the
next command. This leads to a memory context allocated with itself as
a parent and child, triggering an infinite loop when attempting to
delete it. I've written more details in a separate thread[1].
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Naylor | 2025-03-10 08:48:31 | Re: Improve CRC32C performance on SSE4.2 |
| Previous Message | Anthonin Bonnefoy | 2025-03-10 08:07:59 | Re: Memory context can be its own parent and child in replication command |