| From: | Sbob <sbob(at)quadratum-braccas(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pgbench log output |
| Date: | 2022-09-02 16:42:28 |
| Message-ID: | 29c00021-e1ac-422d-e889-a8c5f386aafc@quadratum-braccas.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Perfect! Thanks
On 9/2/22 10:22, David G. Johnston wrote:
> On Fri, Sep 2, 2022 at 9:13 AM Sbob <sbob(at)quadratum-braccas(dot)com> wrote:
>
> However I do not understand what data is represented / how to
> decipher the log file, can someone enlighten me or point me to
> docs that lay this out?
>
> pgbench is a client application since it doesn't require being on the
> server to run - just a connection to a database. So you'd find it
> under the "Client Applications" chapter in the Documentation's Table
> of Contents.
>
> Or just use the Index.
>
> Or search.
>
> https://www.postgresql.org/docs/current/pgbench.html
>
> The section named "Per-Transaction Logging" sounds like it is relevant
> here.
>
> David J.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Wells Oliver | 2022-09-02 21:15:16 | Understanding updates and deadlocks more clearly |
| Previous Message | David G. Johnston | 2022-09-02 16:22:56 | Re: pgbench log output |