Re: Reload configuration more frequently in apply worker.

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: "Zhijie Hou (Fujitsu)" <houzj(dot)fnst(at)fujitsu(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Reload configuration more frequently in apply worker.
Date: 2023-06-07 05:53:35
Message-ID: CAA4eK1Jw8-Wk8nEPpSP8J=35ghSkBEAG82HfPANpv0Y9acpLTA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jun 6, 2023 at 7:45 AM Zhijie Hou (Fujitsu)
<houzj(dot)fnst(at)fujitsu(dot)com> wrote:
>
> On Monday, June 5, 2023 8:03 AM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> >
> >
> > I am able to reproduce the problem with the script and steps mentioned by
> > you. The patch provided by you fixes the problem and looks good to me. I'll
> > push this by Wednesday unless there are any comments/suggestions. Though
> > this problem exists in previous branches as well, but as there are no field
> > reports and the problem also doesn't appear to be a common problem, so I
> > intend to push only for v16. What do you or others think?
>
> Thanks for the review. I agree that we can push only for V16.
>

Pushed.

--
With Regards,
Amit Kapila.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Julien Rouhaud 2023-06-07 06:00:00 Re: confusion about this commit "Revert "Skip redundant anti-wraparound vacuums""
Previous Message Jaime Casanova 2023-06-07 05:32:22 is pg_log_standby_snapshot() really needed?