Re: pgbench --startup option - Mailing list pgsql-hackers

From Fabien COELHO
Subject Re: pgbench --startup option
Date
Msg-id alpine.DEB.2.02.1305022022470.9292@localhost6.localdomain6
Whole thread Raw
In response to Re: pgbench --startup option  (Jeff Janes <jeff.janes@gmail.com>)
Responses Re: pgbench --startup option  (Jeff Janes <jeff.janes@gmail.com>)
List pgsql-hackers
I've just done a quick review of the source, as I've been hacking in 
pgbench myself.

I think that the feature makes sense.

About the details of the patch:

(1) Some changes in the patch are unrelated to the purpose of the patch 
(e.g. spacing changes, error message...), and should be removed?

(2) Instead adding a new function, I would suggest to modify the existing 
one with an added argument, which would be ignored when NULL is passed.

(3) I'm not sure of the behavior of the feature. What if two statements 
are required, should it not be able to handle multiple --startup 
specifications, say with an array instead of a scalar?

(4) C style: there is no need to put a ";" after "}".

(5) In the documentation, other options do not put a "=" sign between the 
option and its argument, although it is also accepted.

Have a nice day,

-- 
Fabien.



pgsql-hackers by date:

Previous
From: Fabien COELHO
Date:
Subject: [PATCH] add long options to pgbench (submission 1)
Next
From: David Fetter
Date:
Subject: Re: GSOC13 proposal - extend RETURNING syntax