Re: repeated decoding of prepared transactions

From: Ajin Cherian <itsajin(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: repeated decoding of prepared transactions
Date: 2021-02-23 09:36:03
Message-ID: CAFPTHDYjsgS9m3PeqRSVS6598FFv-iMPvd0bs+exUqfp0udnTQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Feb 22, 2021 at 8:27 PM Andres Freund <andres(at)anarazel(dot)de> wrote:

> > Yeah, we need to probably store this new point as slot's persistent information.
>
> Should be fine I think...

This idea looks convincing. I'll write up a patch incorporating these changes.

regards,
Ajin Cherian
Fujitsu Australia

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2021-02-23 09:53:49 Re: repeated decoding of prepared transactions
Previous Message Amit Langote 2021-02-23 09:32:53 Re: A reloption for partitioned tables - parallel_workers