Re: Memory context can be its own parent and child in replication command

From: Anthonin Bonnefoy <anthonin(dot)bonnefoy(at)datadoghq(dot)com>
To: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Memory context can be its own parent and child in replication command
Date: 2025-03-10 08:07:59
Message-ID: CAO6_Xqo3tan5cp292buxiutr4TWOHd6aw303BztyNWCd4LUpYw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

The issue seems to have been introduced by 2129d184a206c when
transactionState->priorContext was added and is only present in HEAD.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Anthonin Bonnefoy 2025-03-10 08:41:56 Re: Xact end leaves CurrentMemoryContext = TopMemoryContext
Previous Message Stepan Neretin 2025-03-10 07:58:24 Re: FSM doesn't recover after zeroing damaged page.