Be more careful about newline-chomping in pgbench.
process_backslash_command would drop the last character of the input
command on the assumption that it was a newline. Given a non newline
terminated input file, this could result in dropping the last character
of the command. Fix that by doing a
Fix some subtle problems in pgbench transaction stats counting.
With --latency-limit, transactions might get skipped even beyond the
transaction count limit specified by -t, throwing off the expected
number of transactions and thus the denominator for later stats.
Be sure to stop skipping transact
Adjust pgbench to allow non-ASCII characters in variable names.
This puts it in sync with psql's notion of what is a valid variable name.
Like psql, we document that "non-Latin letters" are allowed, but actually
any non-ASCII character is accepted.
Fabien Coelho
Discussion:
https://postgr.es/m/
Fix translatable string
Discussion: https://postgr.es/m/20170828130545.sdajqlpr37hmmd6a@alvherre.pgsql
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/863d75439e8733b4bf6195a2c8a09966f04d8fbe
Modified Files
--
src/bin/pg_rewind/libpq_fetch.c | 10 ++
Fix translatable string
Discussion: https://postgr.es/m/20170828130545.sdajqlpr37hmmd6a@alvherre.pgsql
Branch
--
REL_10_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/a1af1e7cfaefbef38e6b85ac632ed488744b3fd0
Modified Files
--
src/bin/pg_rewind/libpq_fetch.c | 10
Fix translatable string
Discussion: https://postgr.es/m/20170828130545.sdajqlpr37hmmd6a@alvherre.pgsql
Branch
--
REL9_6_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/bd75335a83bf0564d6d256d1b78499a5ea489d74
Modified Files
--
src/bin/pg_rewind/libpq_fetch.c | 10
