Re: pgbench - refactor init functions with buffers

Поиск
Список
Период
Сортировка
От Dilip Kumar
Тема Re: pgbench - refactor init functions with buffers
Дата
Msg-id CAFiTN-vNQOAxT3STgJT4caMkv=kMEoaWA-4j9jU+ZWsaJqMTbA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: pgbench - refactor init functions with buffers  (Fabien COELHO <coelho@cri.ensmp.fr>)
Список pgsql-hackers
On Tue, Oct 22, 2019 at 3:30 PM Fabien COELHO <coelho@cri.ensmp.fr> wrote:
>
>
> 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.
>
I see.  I was under impression that we don't use this style in PG.
But, since we are already using this style other places so no
objection from my side for this particular point.
Sorry for the noise.

-- 
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com



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

Предыдущее
От: Pavel Stehule
Дата:
Сообщение: Re: dropdb --force
Следующее
От: Jeevan Ladhe
Дата:
Сообщение: Re: pgbench - refactor init functions with buffers