pgbench -T isn't a hard cutoff.

Поиск
Список
Период
Сортировка
От mark
Тема pgbench -T isn't a hard cutoff.
Дата
Msg-id 005a01cc6467$410a87c0$c31f9740$@com
обсуждение исходный текст
Ответы Re: pgbench -T isn't a hard cutoff.  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: pgbench -T isn't a hard cutoff.  (Greg Smith <greg@2ndQuadrant.com>)
Список 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 по дате отправления:

Предыдущее
От: Devrim GÜNDÜZ
Дата:
Сообщение: Re: BUG #6179: "service postgresql-9.0 stop" does not stop postgresql server
Следующее
От: Tom Lane
Дата:
Сообщение: Re: pgbench -T isn't a hard cutoff.