Re: BackgroundPsql's set_query_timer_restart() may not work
Masahiko Sawada <sawada.mshk@gmail.com>
From: Masahiko Sawada <sawada.mshk@gmail.com>
To: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2023-11-29T08:19:11Z
Lists: pgsql-hackers
Attachments
- v2-0001-Fix-set_query_timer_restart-didn-t-work-without-a.patch (application/octet-stream) patch v2-0001
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
Commits
-
Fix BackgroundPsql's set_query_timer_restart() issue without argument.
- c684d7c80f5c 16.2 landed
- f99dd98242d4 17.0 landed
-
Refactor background psql TAP functions
- 664d757531e1 16.0 cited