steve-chavez 7e99babec7 feat: log pool maximum size ...

It's important for observability to have an historic trace of the pool
size. Currently we expose it on the metrics endpoint, but not all
deployments use it.

This logs the pool size after the successful connection log to make it
more visible:

<timestamp>: Connection Pool initialized with a maximum size of 4 connections

2024-10-02 22:47:22 -05:00

..

api

docs: rpc example for array of json objects

2024-08-23 13:01:43 -05:00

admin_server.rst

docs: add "config" and "schema_cache" endpoints to the admin server

2024-05-22 19:16:01 -05:00

api.rst

docs: Fix broken redirects in api.rst

2024-02-21 09:40:11 +01:00

auth.rst

docs: Rename Stored Procedures to Functions consistently

2024-02-21 09:40:11 +01:00

cli.rst

docs: shorten CLI

2024-05-24 18:05:45 -05:00

configuration.rst

config forbid same server-port and admin-server-port (#3559)

2024-07-03 13:02:02 -05:00

connection_pool.rst

docs: better place for application_name

2024-05-06 11:12:45 -05:00

errors.rst

fix: fix incorrect 413 error on pg 54* errors

2024-05-20 18:59:33 -05:00

listener.rst

docs: add listener recovery

2024-06-25 20:03:22 -05:00

observability.rst

feat: log pool maximum size

2024-10-02 22:47:22 -05:00

schema_cache.rst

docs: add "Listener" page

2024-06-12 18:19:16 -05:00

transactions.rst

docs: rename to hoisted function settings

2024-08-01 19:17:56 -05:00