From: | Kristjan Mustkivi <sonicmonkey(at)gmail(dot)com> |
---|---|
To: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Pgbouncer, docker and systemd |
Date: | 2022-04-19 13:01:07 |
Message-ID: | CAOQPKaszN=425jdESsGOSxCYP4yL8skpwuAVB4y=Qb1CmpJNdw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Dear all,
Iam curious if anyone has tried to marry dockerized pgbouncer and systemd?
Why? To get my own most up to date pgbouncer version independent of
the OS provided package and coupled with systemd's offered port reuse
and separate management ports.
I happened to read
* https://www.2ndquadrant.com/en/blog/running-multiple-pgbouncer-instances-with-systemd/
* https://www.enterprisedb.com/postgres-tutorials/pgbouncer-setup-extended-architecture-use-cases-and-leveraging-soreuseport
The main problem has been that the sd_notify call will not get out
from the container and the host's systemctl start is left hanging
until a timeout occurs. And I have compiled my own pgbouncer
--with-systemd flag so it is probably a docker container feature.
Cheers,
--
Kristjan Mustkivi
Email: kristjan(dot)mustkivi(at)gmail(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Gande Harshith | 2022-04-19 13:42:45 | GSoC: <New and improved website for pgjdbc (JDBC) (2022)> |
Previous Message | Ram Pratap Maurya | 2022-04-19 04:41:44 | RE: Huge archive log generate in Postgresql-13 |