| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Victor Sudakov <vas(at)sibptus(dot)ru>, pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pgbouncer logs and its efficiency |
| Date: | 2022-02-02 07:08:40 |
| Message-ID: | 2d4321bd-0174-42c9-3671-fa9626326d10@enterprisedb.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On 28.01.22 05:14, Victor Sudakov wrote:
> 1. What is the meaning of those IDs in the log like
> "S-0xaaaae460fcb0", "C-0xaaaae45d9fb0" ? I suspect that "S-" and "C-"
> mean "server" and "client", but what are those HEX numbers?
These are the internal addresses of the server and client structures.
You can use those to track a particular server or client connection
through the logs and through SHOW SERVERS and SHOW SERVERS.
> 2. How would you calculate the efficiency of pgbouncer, like
> client_conns/server_conns ratio (current and average over over time)?
This depends heavily on what you are using pgbouncer for and what
metrics are relevant for your application.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Holger Jakobs | 2022-02-02 07:16:00 | Re: Determine potential change in table size after a column dropped? |
| Previous Message | Laurenz Albe | 2022-02-01 15:48:18 | Re: Determine potential change in table size after a column dropped? |