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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Anthonin Bonnefoy <anthonin(dot)bonnefoy(at)datadoghq(dot)com>
Cc: 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-11 00:09:16
Message-ID: Z89_LC8ovVHvPE6_@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Mar 10, 2025 at 09:07:59AM +0100, Anthonin Bonnefoy wrote:
> The issue seems to have been introduced by 2129d184a206c when
> transactionState->priorContext was added and is only present in HEAD.

It seems to me that you mean 1afe31f03cd2, no?
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Maciek Sakrejda 2025-03-11 00:11:48 Question about duplicate JSONTYPE_JSON check
Previous Message Michael Paquier 2025-03-11 00:06:27 Re: per backend WAL statistics