Re: BackgroundPsql's set_query_timer_restart() may not work - Mailing list pgsql-hackers

From Masahiko Sawada
Subject Re: BackgroundPsql's set_query_timer_restart() may not work
Date
Msg-id CAD21AoBvu-KcjOFSCXG=AzKsZ3PymqK8iZnCVBgehBcgY1hgVA@mail.gmail.com
Whole thread Raw
In response to Re: BackgroundPsql's set_query_timer_restart() may not work  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
Responses Re: BackgroundPsql's set_query_timer_restart() may not work
List pgsql-hackers
On Wed, Nov 29, 2023 at 4:30 PM Bharath Rupireddy
<bharath.rupireddyforpostgres@gmail.com> wrote:
>
> On Tue, Nov 28, 2023 at 12:23 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> >
> > Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com> writes:
> > > A nitpick on the patch - how about honoring the passed-in parameter
> > > with something like $self->{query_timer_restart} = 1 if !defined
> > > $self->{query_timer_restart}; instead of just setting it to 1 (a value
> > > other than undef) $self->{query_timer_restart} = 1;?
> >
> > I wondered about that too, but the evidence of existing callers is
> > that nobody cares.  If we did make the code do something like that,
> > (a) I don't think your fragment is right, and (b) we'd need to rewrite
> > the function's comment to explain it.  I'm not seeing a reason to
> > think it's worth spending effort on.

Agreed.

> Hm. I don't mind doing just the $self->{query_timer_restart} = 1; like
> in Sawada-san's patch.

Okay, I've attached the patch that I'm going to push through v16,
barring any objections.

Regards,

--
Masahiko Sawada
Amazon Web Services: https://aws.amazon.com

Attachment

pgsql-hackers by date:

Previous
From: Bharath Rupireddy
Date:
Subject: Re: BackgroundPsql's set_query_timer_restart() may not work
Next
From: "Zhijie Hou (Fujitsu)"
Date:
Subject: RE: Synchronizing slots from primary to standby