Using the -T flag in pgbench I noticed that -T is a just a effort rather than a hard cut off.
With a (misbehaving) pooler and a "large" number of clients+jobs it's possible to have the pgbench run extend by several seconds or even minutes past the allotted time by -T. (or hang indefinitely if the transactions never complete due to pooler issues.) Expected behavior would be -T would mean a hard cut off. Thoughts ? -Mark -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
