Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nh3SP-0001EH-WB for pgsql-admin@arkaria.postgresql.org; Wed, 20 Apr 2022 06:04:54 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nh3SO-0001hx-Nt for pgsql-admin@arkaria.postgresql.org; Wed, 20 Apr 2022 06:04:52 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nh3SO-0001eY-D0 for pgsql-admin@lists.postgresql.org; Wed, 20 Apr 2022 06:04:52 +0000 Received: from mail-pl1-x62e.google.com ([2607:f8b0:4864:20::62e]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nh3SK-0006EE-Jo for pgsql-admin@lists.postgresql.org; Wed, 20 Apr 2022 06:04:52 +0000 Received: by mail-pl1-x62e.google.com with SMTP id s17so874933plg.9 for ; Tue, 19 Apr 2022 23:04:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=BADAsD3W0QcRnxJd8NRm/x9qrqkWfgtkmpIGJhFR8uA=; b=IJr7Ber1h3D2x3HY1z2nSSMfBRtfDMHeqTXnGK7YBlgI2AUz1v0rXYIL8tABHWBhrP U9zblRHw2t+aChqMs+Z5idkL98sRfVIZlMcE9RAEvWE3LWYe3cc9XvTfZ2PSmoVlFuQ4 K/npeQ+KQVbi5vFgz46247CrirVYAl4viLzLHmbu5n5ArEhHJhR2gmXUlTsEfmb9Gvf8 BXEhX8x8Z8ORDlkNPuytVZicxGQKBqXxfE2TnPbJn+79xGJBSGv7SjDrUeRLpptJ41SW zrA1qsChDvZpxaGvjqbh6PGYkR5d7inPzR4tLz+0SOadqqdvbNZFac+niC8qCDAeFAz+ qy9g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=BADAsD3W0QcRnxJd8NRm/x9qrqkWfgtkmpIGJhFR8uA=; b=MPOXcflJaST7ZX21qJllGW4ONlYQKp/JlhKWmp457fftG/5Zvt7pXfp4KInK8gO9kx SqsyNXhB8AY30obIscCccgkuJHVP6EXx1Z6FjHVLmTgScMN9+08f2Z8GtWogYooCT4a0 tbKTnt0Td9lpHmLaD6NlbGWHynnRvw8PI3ktmjPfcyBPs1DeIjDvYqHPdE9CPop32k+y hzu4OjwwUkiwWY6w/heh1yKJbaENl4z3fO5B9/mYk5onRADyms9vp+537mcDPpaaRQLq X6a+OWN5OgnVSSWjBDVq6pJP2rCNXbCRTeDqc1W8RtYS5TVBg/bIKKMb/Pv/mwqtPDr0 3vOw== X-Gm-Message-State: AOAM530UP9diSIvfWX4uVGj3cLwzLRCj2exTqDgcdpH79XZxvjVDNNK+ /4zo4t3ltzIAHq7p51XizsMdFM3IaAQtRaBROAY= X-Google-Smtp-Source: ABdhPJw7Oitq70WdN4m1UaRvNTzzhHG/WHtjOrJwur6dYtWHxRutWnrN9LkNY+f8YjgCum+/GtOQzH9s7Pfy+xDapco= X-Received: by 2002:a17:90a:5601:b0:1d2:d49a:c3d8 with SMTP id r1-20020a17090a560100b001d2d49ac3d8mr2583938pjf.113.1650434686572; Tue, 19 Apr 2022 23:04:46 -0700 (PDT) MIME-Version: 1.0 References: <250e40d4-a750-c960-3586-a01d99c780f2@enterprisedb.com> In-Reply-To: <250e40d4-a750-c960-3586-a01d99c780f2@enterprisedb.com> From: Kristjan Mustkivi Date: Wed, 20 Apr 2022 09:04:35 +0300 Message-ID: Subject: Re: Pgbouncer, docker and systemd To: Peter Eisentraut Cc: pgsql-admin@lists.postgresql.org Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, Apr 19, 2022 at 5:08 PM Peter Eisentraut wrote: > > 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. Makes sense. Of course, there's a bit more: the environment where the pgbouncer would be installed hosts different services packaged by many teams and the standard for packaging is docker. I will figure out a different approach. Thank you for the comments! Best regards, -- Kristjan Mustkivi Email: kristjan.mustkivi@gmail.com