| From: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com> |
|---|---|
| To: | 'ikedarintarof' <ikedarintarof(at)oss(dot)nttdata(dot)com> |
| Cc: | "slpmcf(at)gmail(dot)com" <slpmcf(at)gmail(dot)com>, "boekewurm+postgres(at)gmail(dot)com" <boekewurm+postgres(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Srinath Reddy Sadipiralla <srinath2133(at)gmail(dot)com>, Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
| Subject: | RE: Suggestion to add --continue-client-on-abort option to pgbench |
| Date: | 2025-06-04 12:57:14 |
| Message-ID: | OSCPR01MB149669D1C9FD9710AF629518BF56CA@OSCPR01MB14966.jpnprd01.prod.outlook.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dear Ikeda-san,
Thanks for starting the new thread! I have never known the issue before I heard at
PGConf.dev.
Few comments:
1.
This parameter seems a type of benchmark option. So should we set
benchmarking_option_set as well?
2.
Not sure, but exit-on-abort seems a similar option. What if both are specified?
Is it allowed?
3.
Can you consider a test case for the new parameter?
Best regards,
Hayato Kuroda
FUJITSU LIMITED
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Xuneng Zhou | 2025-06-04 12:59:50 | Request to Expedite Account Activation Cool-Off Period |
| Previous Message | Andrei Lepikhov | 2025-06-04 12:52:04 | Re: MergeAppend could consider sorting cheapest child path |