From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
---|---|
To: | Kristjan Mustkivi <sonicmonkey(at)gmail(dot)com>, pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: Pgbouncer, docker and systemd |
Date: | 2022-04-19 14:08:21 |
Message-ID: | 250e40d4-a750-c960-3586-a01d99c780f2@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On 19.04.22 15:01, Kristjan Mustkivi wrote:
> 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.
I think for your what you are trying to set up here, docker and systemd
are competing approaches for launching services and they will fight or
hinder each other.
If all you want is an up to date pgbouncer package, perhaps you will
find what you need on apt.postgresql.org or yum.postgresql.org.
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2022-04-19 17:20:51 | Re: Huge archive log generate in Postgresql-13 |
Previous Message | Gande Harshith | 2022-04-19 13:42:45 | GSoC: <New and improved website for pgjdbc (JDBC) (2022)> |