From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: few ideas for pgbench |
Date: | 2021-05-04 19:10:10 |
Message-ID: | CAFj8pRA8awtHFgpMafNDqXjqnqg0frrH_Hgg4+vcaWtTnKED=g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
út 4. 5. 2021 v 20:59 odesílatel Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> napsal:
>
> Hello Pavel,
>
> > 1. print server version to the output of pgbench. Now only client side
> > version is printed
>
> It is easy enough and makes sense. Maybe only if it differs from the
> client side version ?
>
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.
> > 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.
> --
> Fabien.
>
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2021-05-04 19:18:36 | Re: [bug?] Missed parallel safety checks, and wrong parallel safety |
Previous Message | Robert Haas | 2021-05-04 19:09:05 | Re: [bug?] Missed parallel safety checks, and wrong parallel safety |