Re: BackgroundPsql's set_query_timer_restart() may not work
От | Bharath Rupireddy |
---|---|
Тема | Re: BackgroundPsql's set_query_timer_restart() may not work |
Дата | |
Msg-id | CALj2ACXnRta9Je5tBTkGz0Pg1M0oAAcVhowrmk4p_8ZU2nMFeg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: BackgroundPsql's set_query_timer_restart() may not work (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: BackgroundPsql's set_query_timer_restart() may not work
|
Список | pgsql-hackers |
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. Hm. I don't mind doing just the $self->{query_timer_restart} = 1; like in Sawada-san's patch. -- Bharath Rupireddy PostgreSQL Contributors Team RDS Open Source Databases Amazon Web Services: https://aws.amazon.com
В списке pgsql-hackers по дате отправления: