Re: Unexpected changes of CurrentResourceOwner and CurrentMemoryContext

From: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Cc: Euler Taveira <euler(at)eulerto(dot)com>, Antonin Houska <ah(at)cybertec(dot)at>, Mihail Nikalayeu <mihailnikalayeu(at)gmail(dot)com>, rmt(at)postgresql(dot)org
Subject: Re: Unexpected changes of CurrentResourceOwner and CurrentMemoryContext
Date: 2026-07-15 16:27:19
Message-ID: alewd1f2G0kKeM1i@alvherre.pgsql
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2025-Sep-12, Álvaro Herrera wrote:

> I have pushed it with that change. I'll also add an open item for pg19
> so that we remember to come back to remove the assertions, if we feel we
> no longer need them.

We have received no reports of this new assertion being hit. I think we
can remove it now, as we said back in September.

https://postgr.es/m/flat/119497(dot)1756892972(at)localhost

(We could also remove it right before RC, actually.)

Any thoughts?

--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"No nos atrevemos a muchas cosas porque son difíciles,
pero son difíciles porque no nos atrevemos a hacerlas" (Séneca)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tristan Partin 2026-07-15 16:30:47 Re: meson: avoid PATH bloat from NLS .mo targets in tmp_install test setup
Previous Message Álvaro Herrera 2026-07-15 16:14:30 Re: NULL pointer dereference in syslogger with load_libraries() and -DEXEC_BACKEND at startup