From: Achilleas Mantzios <achill@matrix.gatewaynet.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: pgpool versus which tool?
Date: Mon, 15 Oct 2018 13:34:41 +0300
Message-ID: <d7bf0b86-bee9-f411-df26-de54c74352ad@matrix.gatewaynet.com> (raw)
In-Reply-To: <CAON0DazNfUSGJ5d2fHbPK1bOEJPx=kGmcn3CF0+L9o0a8ZE31Q@mail.gmail.com>
References: <CABG8FoO4f=V8EWE0n8ofnU4ph6Nygpu964ZtiUF4X9fQGO7x8A@mail.gmail.com>
<e242051d-1150-e3d5-6964-60b2538de067@gmx.net>
<CAON0DazNfUSGJ5d2fHbPK1bOEJPx=kGmcn3CF0+L9o0a8ZE31Q@mail.gmail.com>
In the case of PAM authentication (the only way to do LDAP authentication) pgbouncer is haunted by some nasty bug(s) : https://github.com/pgbouncer/pgbouncer/issues/285
I don't know if pgpool handles PAM better under stress.
On 15/10/18 1:00 μ.μ., Prince Pathria wrote:
> Hey Pierre,
>
> go for pgBouncer if you want transaction based pooling and if your sole aim to use pgPool is for pooling then better go for pgBouncer.
> pgBouncer performs 3x better than pgpool-II in benchmarking results.
>
> Thanks!
> Prince Pathria
> Systems Architect Evive +91 9478670472 goevive.com <http://goevive.com;
>
>
> On Mon, Oct 15, 2018 at 1:52 PM Thomas Kellerer <spam_eater@gmx.net <mailto:spam_eater@gmx.net>> wrote:
>
> Pierre Ochsenbein schrieb am 15.10.2018 um 09:38:
> > Which best of tool you recommend to replace pgpool?
> What's wrong with pgPool that you think you need to replace it?
>
> And what is you requirement for such a tool?
>
--
Achilleas Mantzios
IT DEV Lead
IT DEPT
Dynacom Tankers Mgmt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: achill@matrix.gatewaynet.com, pgsql-admin@lists.postgresql.org
Subject: Re: pgpool versus which tool?
In-Reply-To: <d7bf0b86-bee9-f411-df26-de54c74352ad@matrix.gatewaynet.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox