Re: Unexpected changes of CurrentResourceOwner and CurrentMemoryContext

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

Álvaro Herrera <alvherre(at)kurilemu(dot)de> wrote:

> 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?

No objections here.

--
Antonin Houska
Web: https://www.cybertec-postgresql.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Philip Alger 2026-07-17 12:47:45 Re: [PATCH] Add pg_get_trigger_ddl() to retrieve the CREATE TRIGGER statement
Previous Message Antonin Houska 2026-07-17 12:15:52 Re: Batching in executor