pgbench -T isn't a hard cutoff.

From: "mark" <dvlhntr(at)gmail(dot)com>
To: <pgsql-bugs(at)postgresql(dot)org>
Subject: pgbench -T isn't a hard cutoff.
Date: 2011-08-27 03:13:10
Message-ID: 005a01cc6467$410a87c0$c31f9740$@com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2011-08-27 04:56:24 Re: pgbench -T isn't a hard cutoff.
Previous Message Devrim GÜNDÜZ 2011-08-26 16:04:27 Re: BUG #6179: "service postgresql-9.0 stop" does not stop postgresql server