From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Durumdara <durumdara(at)gmail(dot)com>, Melvin Davidson <melvin6925(at)gmail(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Maximum of connections in PG |
Date: | 2017-03-14 18:04:00 |
Message-ID: | 364aa322-86b6-2aa0-1861-a1eb84e55763@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 03/14/2017 09:08 AM, Durumdara wrote:
> Dear Melvin!
>
> What is the meaning of PgBouncer with persistent, non-interruptable
> connections? To I know it (for learn).
>
> They are non web connections (request, get connection, result, drop
> connection), they are pure, native applications which are keeping
> connection from the start to the termination.
So just so we are same page:
1) When you say Web connections you are referring to HTTP:
*connection*
client request --> Web Server
|
client <-- reponse |
*connection*
repeat *connection* section for each request
2) Postgres connections
*connection*
client connect -->
query --> Postgres server
query -->
client disconnect <--
*connection*
In either case you are connecting/disconnecting it is just a matter of
when. So if I am following correctly you do not actually need a
connection to the Postgres server that is always on you just need one to
be available when you run a query or set of queries.
>
> Thank you!
>
> dd
>
>
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2017-03-14 18:18:09 | Re: UPDATE ... ON CONFLICT DO NOTHING |
Previous Message | Melvin Davidson | 2017-03-14 17:04:13 | Re: Maximum of connections in PG |