Re: Logical replication timeout

From: vignesh C <vignesh21(at)gmail(dot)com>
To: "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>
Cc: RECHTÉ Marc <marc(dot)rechte(at)meteo(dot)fr>, Shlok Kyal <shlok(dot)kyal(dot)oss(at)gmail(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Logical replication timeout
Date: 2024-12-27 04:11:00
Message-ID: CALDaNm2eWmtcr-v9Q-AuhM66capAp0w758PTtfwmUWdSOq6Jvg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 25 Dec 2024 at 13:55, Hayato Kuroda (Fujitsu)
<kuroda(dot)hayato(at)fujitsu(dot)com> wrote:
>
> Dear Marc,
>
> > Thanks again for this new patch.
> >
> > Unfortunately it does not compile (17.2 source):
>
> Right, because of the reason I posted [1].
>
> I updated the patch which did the same approach. It could pass my CI.

Let's conduct some performance tests with varying numbers of spill
files (e.g., small ones like 1, 5, and 10, and larger ones like 100,
1000, and 10,000) along with different levels of concurrent
transactions. We can then compare the results with the current HEAD.

Regards,
Vignesh

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Richard Guo 2024-12-27 04:16:07 Re: ERROR: corrupt MVNDistinct entry
Previous Message Michael Paquier 2024-12-27 04:00:37 Re: PoC: history of recent vacuum/checkpoint runs (using new hooks)