Re: few ideas for pgbench

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: few ideas for pgbench
Date: 2021-05-05 09:55:32
Message-ID: alpine.DEB.2.22.394.2105051152100.2553649@pseudo
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Hello Pavel,

> This is not a simple question. Personally I prefer to show this info every
> time, although it can be redundant. Just for check and for more simple
> automatic processing.
>
> When I run pgbench, I usually work with more releases together, so the
> server version is important info.

Ok. Yes.

>>> 2. can ve generate some output in structured format - XML, JSON ?
>>
>> It is obviously possible, but that would mean some code. ISTM that the
>> various outputs are easy enough to parse and convert to anything without
>> needing a special format? Is there some particular part you have in mind?
>>
>
> I thought about something what I can simply import to Postgres or to R.
> But maybe XML or JSON is a bad idea.
>
> What about CSV? Any run can produce one row.

Yep, CSV is simple and nice. It depends on what information you would
like. For instance for progress report (-P 1) or logs/sampling (-l) would
be relevant candidates for CSV. Not so much for the final report, though.

--
Fabien.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Laurenz Albe 2021-05-05 10:03:08 Re: Update maintenance_work_mem/autovacuum_work_mem to reflect the 1GB limitation with VACUUM
Previous Message Laurenz Albe 2021-05-05 09:55:20 Re: Clarify how triggers relate to transactions