Re: pgsql: Allow pgbench to exit immediately when any client is aborted.
От | Tatsuo Ishii |
---|---|
Тема | Re: pgsql: Allow pgbench to exit immediately when any client is aborted. |
Дата | |
Msg-id | 20230830.132320.1227661966607060791.t-ishii@sranhm.sra.co.jp обсуждение исходный текст |
Ответ на | Re: pgsql: Allow pgbench to exit immediately when any client is aborted. (Michael Paquier <michael@paquier.xyz>) |
Список | pgsql-committers |
> Hi Ishii-san, > > On Wed, Aug 30, 2023 at 01:05:15AM +0000, Tatsuo Ishii wrote: >> Allow pgbench to exit immediately when any client is aborted. >> >> Previously when client was aborted due to some error during >> benchmarking, other clients continued their run until certain number >> of transactions specified -t was reached or the time specified by -T >> was expired. At the end, the results are printed with caution: "Run >> was aborted; the above results are incomplete" shows. >> >> New option "--exit-on-abort" allows pgbench to exit immediately in >> this case so that users could quickly fix the cause of the failure and >> try again another round of benchmarking. > > Buildfarm member koel is saying that this commit was not properly > indented: > https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=koel&dt=2023-08-30%2002%3A19%3A02 > > Could you address this with a run of pgindent? > > After the reindent is itself committed, you should also add the commit > that did the indentation to .git-blame-ignore-revs. Ok, I will do it. Best reagards, -- Tatsuo Ishii SRA OSS LLC English: http://www.sraoss.co.jp/index_en/ Japanese:http://www.sraoss.co.jp
В списке pgsql-committers по дате отправления: