pgbench -T isn't a hard cutoff. - Mailing list pgsql-bugs

From mark
Subject pgbench -T isn't a hard cutoff.
Date
Msg-id 005a01cc6467$410a87c0$c31f9740$@com
Whole thread Raw
Responses Re: pgbench -T isn't a hard cutoff.
Re: pgbench -T isn't a hard cutoff.
List 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

pgsql-bugs by date:

Previous
From: Devrim GÜNDÜZ
Date:
Subject: Re: BUG #6179: "service postgresql-9.0 stop" does not stop postgresql server
Next
From: Tom Lane
Date:
Subject: Re: pgbench -T isn't a hard cutoff.