Re: few ideas for pgbench - Mailing list pgsql-hackers

From Fabien COELHO
Subject Re: few ideas for pgbench
Date
Msg-id alpine.DEB.2.22.394.2105051152100.2553649@pseudo
Whole thread Raw
In response to Re: few ideas for pgbench  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: few ideas for pgbench
List 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.



pgsql-hackers by date:

Previous
From: Jakub Wartak
Date:
Subject: RE: Use simplehash.h instead of dynahash in SMgr
Next
From: Pavel Stehule
Date:
Subject: Re: few ideas for pgbench