On Mon, Sep 30, 2019 at 5:17 PM Fabien COELHO <coe...@cri.ensmp.fr> wrote: > > > > I don't want to introduce a new pattern in tests which people can then > > tomorrow copy at other places even though such code is not required. > > OTOH, if there is a genuine need for the same, then I am fine. > > Hmmm. The committer is right by definition. Here is a version without > escaping but with a comment instead. >
Thanks, attached is a patch with minor modifications which I am
planning to push after one more round of review on Thursday morning
IST unless there are more comments by anyone else.
The changes include:
1. ran pgindent
2. As per Alvaro's suggestions move few function definitions.
3. Changed one or two comments and fixed spelling at one place.
The one place where some suggestion might help:
+ else if (PQntuples(res) == 0)
+ {
+ /*
+ * This case is unlikely as pgbench already found "pgbench_branches"
+ * above to compute the scale.
+ */
+ fprintf(stderr,
+ "no pgbench_accounts table found in search_path\n"
+ "Perhaps you need to do initialization (\"pgbench -i\") in database
\"%s\"\n", PQdb(con));
+ exit(1);
+ }
Can anyone else think of a better error message either in wording or
style for above case?
--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
pgbench-init-partitioned-21.patch
Description: Binary data
