RE: pgbench bug candidate: negative "initial connection time"

From: "kuroda(dot)hayato(at)fujitsu(dot)com" <kuroda(dot)hayato(at)fujitsu(dot)com>
To: 'Fabien COELHO' <coelho(at)cri(dot)ensmp(dot)fr>
Cc: "'pgsql-hackers(at)lists(dot)postgresql(dot)org'" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: RE: pgbench bug candidate: negative "initial connection time"
Date: 2021-06-14 00:42:12
Message-ID: TYAPR01MB58667A59DF050DAB01CC92F7F5319@TYAPR01MB5866.jpnprd01.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Dear Fabien,

Thank you for replying!

> Hmmm. Possibly. Another option could be not to report anything after some
> errors. I'm not sure, because it would depend on the use case. I guess the
> command returned an error status as well.

I did not know any use cases and decisions , but I vote to report nothing when error occurs.

Best Regards,
Hayato Kuroda
FUJITSU LIMITED

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tatsuo Ishii 2021-06-14 00:42:56 Re: Error on pgbench logs
Previous Message Michael Paquier 2021-06-14 00:27:16 Re: Move pg_attribute.attcompression to earlier in struct for reduced size?