Am 15.11.2018 um 16:14 schrieb Andreas Kretschmer:
Am 15.11.2018 um 16:09 schrieb Mark Moellering:
I can see how, for only a few (hundreds to thousands) of users, the
latter might make more sense but if I need to scale up to millions, I
might not want all of those connections open.
consi
On 11/15/18 7:09 AM, Mark Moellering wrote:
So, I am working on some system designs for a web application, and I
wonder if there is any definitive answer on how to best connect to a
postgres database.
I could have it so that each time a query, or set of queries, for a
particular request, need
Oh, excellent. I knew I was about to reinvent the wheel.
Sometimes, there are just too many new things to keep up on.
Thank you so much!
On Thu, Nov 15, 2018 at 10:16 AM Adrian Klaver
wrote:
> On 11/15/18 7:09 AM, Mark Moellering wrote:
> > So, I am working on some system designs for a web app
Am 15.11.2018 um 16:09 schrieb Mark Moellering:
I can see how, for only a few (hundreds to thousands) of users, the
latter might make more sense but if I need to scale up to millions, I
might not want all of those connections open.
consider a connection-pooler like phbouncer.
Regards, And
So, I am working on some system designs for a web application, and I wonder
if there is any definitive answer on how to best connect to a postgres
database.
I could have it so that each time a query, or set of queries, for a
particular request, needs to be run, a new connection is opened, queries
