Re: pgbench - refactor init functions with buffers

From: Jeevan Ladhe <jeevan(dot)ladhe(at)enterprisedb(dot)com>
To: Dilip Kumar <dilipbalaut(at)gmail(dot)com>
Cc: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pgbench - refactor init functions with buffers
Date: 2019-10-22 09:21:47
Message-ID: CAOgcT0N66ABbmMwEJaXOfF=WZWrSegk9yt=Ybt7DTFHTb3ZzVw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>
>
> 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?
>

+1.

The patch does not apply on master, needs rebase.
Also, I got some whitespace errors.

I think you can also refactor the function tryExecuteStatement(), and
call your newly added function executeStatementExpect() by passing
an additional flag something like "errorOK".

Regards,
Jeevan Ladhe

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Devrim Gündüz 2019-10-22 09:32:53 v12 pg_basebackup fails against older servers (take two)
Previous Message Dilip Kumar 2019-10-22 08:47:37 Re: Questions/Observations related to Gist vacuum