Re: pgsql: Fix fetching default toast value during decoding of in-progress

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: Amit Kapila <akapila(at)postgresql(dot)org>, pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Fix fetching default toast value during decoding of in-progress
Date: 2024-10-07 13:33:17
Message-ID: CAA4eK1JUiLwmLyw99JNXrr1-9yqJULCjXbiWP2LJue96vQvWcQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Mon, Oct 7, 2024 at 4:16 PM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
>
> On Mon, Oct 7, 2024 at 4:14 PM Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
> >
> > > On 7 Oct 2024, at 12:22, Amit Kapila <akapila(at)postgresql(dot)org> wrote:
> > >
> > > Fix fetching default toast value during decoding of in-progress transactions.
> >
> > v14&v15 on adder seems a bit unhappy in the test_decoding test suite:
> >
>
> oops, will check.
>

I think the reason for the instability of the test in 14 and 15 is
that we don't have a predictable way to start streaming in those
branches. We rely on the size of the reorder buffer. This can vary
based on some background activity autoanalyze or others which can
generate WAL records. So, will think some more on it tomorrow on how
to make it reliable in those two branches. For other branches, we used
GUC debug_logical_replication_streaming to control the streaming
behavior.

--
With Regards,
Amit Kapila.

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Nathan Bossart 2024-10-07 15:56:59 pgsql: Restrict password hash length.
Previous Message Amit Kapila 2024-10-07 10:46:47 Re: pgsql: Fix fetching default toast value during decoding of in-progress