Re: shadow variables - pg15 edition

Поиск
Список
Период
Сортировка
От David Rowley
Тема Re: shadow variables - pg15 edition
Дата
Msg-id CAApHDvqESZZxLrqx==J0qQoQmL=ki40+jC6JZZ0o-StzBq_cMg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: shadow variables - pg15 edition  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Ответы Re: shadow variables - pg15 edition  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Список pgsql-hackers
On Thu, 6 Oct 2022 at 02:34, Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
> A simpler idea might be to just remove the inner declaration, and have
> that block set the outer var.  There's no damage, since the block is
> going to end and not access the previous value anymore.
>
> diff --git a/src/bin/pgbench/pgbench.c b/src/bin/pgbench/pgbench.c
> index aa1a3541fe..91a067859b 100644
> --- a/src/bin/pgbench/pgbench.c
> +++ b/src/bin/pgbench/pgbench.c
> @@ -7506,7 +7506,7 @@ threadRun(void *arg)
>                 /* progress report is made by thread 0 for all threads */
>                 if (progress && thread->tid == 0)
>                 {
> -                       pg_time_usec_t now = pg_time_now();
> +                       now = pg_time_now();    /* not lazy; clobbers outer value */

I didn't want to do it that way because all this code is in a while
loop and the outer "now" will be reused after it's set by the code
above.  It's not really immediately obvious to me what repercussions
that would have, but it didn't seem worth taking any risks.

David



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Greg Nancarrow
Дата:
Сообщение: pg_statsinfo - PG15 support?
Следующее
От: David Rowley
Дата:
Сообщение: Re: shadow variables - pg15 edition