Re: PGBouncer logs explanation required

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема Re: PGBouncer logs explanation required
Дата
Msg-id 60e70ae5-250c-04a3-770b-047dc9d966f5@enterprisedb.com
обсуждение исходный текст
Ответ на PGBouncer logs explanation required  (Shubham Mittal <mittalshubham30@gmail.com>)
Список pgsql-general
On 19.12.21 12:50, Shubham Mittal wrote:
> 2021-11-25 14:45:45.244 IST [18307] LOG C-0x6ae270: 
> sit/postgres@abcdlogin attempt: db=sit user=postgres tls=no
> 2021-11-25 14:45:45.299 IST [18307] LOG S-0x6b4f48: sit/postgres@abcd 
> new connection to server (from abcd)
> 2021-11-25 14:46:17.843 IST [18307] LOG S-0x6b4d10: sit/postgres@abcd 
> *closing because: query timeout (age=185s)*
> 2021-11-25 14:46:17.843 IST [18307] LOG C-0x6ae038: sit/postgres@abcd 
> *closing because: query timeout (age=185s)*
> 2021-11-25 14:46:17.843 IST [18307] WARNING C-0x6ae038: 
> sit/postgres@*abcd pooler error: query timeout*
> 2021-11-25 14:46:25.763 IST [18307] LOG stats: 0 xacts/s, 0 queries/s, 
> in 30 B/s, out 141 B/s, xact 3660 us, query 4362 us, wait 152 us
> 
> Does this log mean that connection is closed and returned to the pool 
> and can be reused again?? Or something else?? Please help.

A closed connection cannot be reused, since it's closed.  But after the 
connection is closed, there is a free slot in the pool to possibly open 
a new connection if needed.



В списке pgsql-general по дате отправления:

Предыдущее
От: Matt Magoffin
Дата:
Сообщение: Freeing transient memory in aggregate functions
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Freeing transient memory in aggregate functions