From: | DJ Coertzen <patrolliekaptein(at)gmail(dot)com> |
---|---|
To: | pgsql-performance(at)lists(dot)postgresql(dot)org |
Subject: | psql cli tool and connection pooling |
Date: | 2018-12-21 19:08:33 |
Message-ID: | CALQ6=2BC85A5EZwF8x7MN8bnzkYiw-nijYujjPPdWJUzkjx0jw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
I would love to see a feature on psql cli tool where i can point it to a
connection pool provider back end instead of a postgres host. I read that
pgpool2 emulates a postgres server, but i've never tried it myself. I know
that some languages provide connection pooling, but i'm relying heavily on
psql and its features and i think built-in master/slave connection pooling
in psql cli would make my day, and that of any other dirty bash scripters
out there.
Can anyone comment on their experience with pgpool2 in a high activity
production environment?
Are there other tools or suggestions anyone can point me to?
Is there any appetite to support connection pooling natively by either the
postmaster or the psql cli or some other device that could be contrib to
the source tree?
Does it even matter? Is server version 10 ddos-proof, other than
max_connections?
Thanks.
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Janes | 2018-12-22 00:13:14 | Re: SQL Perfomance during autovacuum |
Previous Message | Merlin Moncure | 2018-12-21 13:40:25 | Re: database crash during pgbench run |