Re: pgbench - refactor init functions with buffers - Mailing list pgsql-hackers

From Fabien COELHO
Subject Re: pgbench - refactor init functions with buffers
Date
Msg-id alpine.DEB.2.21.1910221155310.15559@lancre
Whole thread Raw
In response to Re: pgbench - refactor init functions with buffers  (Dilip Kumar <dilipbalaut@gmail.com>)
Responses Re: pgbench - refactor init functions with buffers
List pgsql-hackers
Hello Dilip,

> - for (i = 0; i < nbranches * scale; i++)
> + for (int i = 0; i < nbranches * scale; i++)
> ...
> - for (i = 0; i < ntellers * scale; i++)
> + for (int i = 0; i < ntellers * scale; i++)
>  {
>
> I haven't read the complete patch.  But, I have noticed that many
> places you changed the variable declaration from c to c++ style (i.e
> moved the declaration in the for loop).  IMHO, generally in PG, we
> don't follow this convention.  Is there any specific reason to do
> this?

There are many places where it is used now in pg (120 occurrences in 
master, 7 in pgbench). I had a bug recently because of a stupidly reused 
index variable, so I tend to use this now it is admissible, moreover here 
I'm actually doing a refactoring patch, so it seems ok to include that.

-- 
Fabien.



pgsql-hackers by date:

Previous
From: Devrim Gündüz
Date:
Subject: v12 pg_basebackup fails against older servers (take two)
Next
From: Amit Kapila
Date:
Subject: Re: Ordering of header file inclusion