pgbench - use enum for meta commands
Minor code enhancement.
While having a look at adding if/elif/else/endif to pgbench, and given the
current gset/cset added meta commands in cf queue, it occured to me that
repeated string comparisons to check for the various meta commands is
neither efficient nor readable. Use an enum instead, which are extensively
used already for other similar purposes.
--
Fabien.
Attachments:
pgbench-enum-meta-1.patchtext/x-diff; name=pgbench-enum-meta-1.patchDownload+42-8
2017-09-23 5:45 GMT+02:00 Fabien COELHO <coelho@cri.ensmp.fr>:
Minor code enhancement.
While having a look at adding if/elif/else/endif to pgbench, and given the
current gset/cset added meta commands in cf queue, it occured to me that
repeated string comparisons to check for the various meta commands is
neither efficient nor readable. Use an enum instead, which are extensively
used already for other similar purposes.
+1
Pavel
Show quoted text
--
Fabien.--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
The following review has been posted through the commitfest application:
make installcheck-world: tested, passed
Implements feature: tested, passed
Spec compliant: tested, passed
Documentation: tested, passed
Hi,
Looks good to me.
The only thing I'm not quite sure about is a comment "which meta command ...".
Maybe it's better to write it without question word, something like "meta command identifier..."?
The new status of this patch is: Ready for Committer
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
The only thing I'm not quite sure about is a comment "which meta command
...". Maybe it's better to write it without question word, something
like "meta command identifier..."?
Ok. I agree.
Updated version attached. I also added a const on a function parameter.
Just a note about the motivation: I want to add the same "\if" syntax
added to psql, but it requires to look at the meta command in a number of
places to manage the automaton status, and the strcmp solution looked both
ugly and inefficient. So this small refactoring is just a preliminary to
the "\if" patch, some day, after this one get committed, if it gets
committed.
The new status of this patch is: Ready for Committer
Thanks for the review.
--
Fabien.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Updated version attached.
<sigh>. Here is the patch. Sorry for the noise.
--
Fabien.
Attachments:
pgbench-enum-meta-2.patchtext/x-diff; name=pgbench-enum-meta-2.patchDownload+42-8
On Thu, 2 Nov 2017 17:50:52 +0100 (CET)
Fabien COELHO <coelho@cri.ensmp.fr> wrote:
Updated version attached.
<sigh>. Here is the patch. Sorry for the noise.
Everything alright. Patch is ready for commiter.
--
Aleksandr Parfenov
Postgres Professional: http://www.postgrespro.com
Russian Postgres Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Fabien COELHO <coelho@cri.ensmp.fr> writes:
[ pgbench-enum-meta-2.patch ]
Pushed with some trivial cosmetic adjustments (pgindent changed
it more than I did).
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
[ pgbench-enum-meta-2.patch ]
Pushed with some trivial cosmetic adjustments (pgindent changed
it more than I did).
Ok. Thanks.
--
Fabien.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers