Re: Designing a better connection pool for psycopg3 - Mailing list psycopg

From Daniele Varrazzo
Subject Re: Designing a better connection pool for psycopg3
Date
Msg-id CA+mi_8aMCUW873qcN1vghtMQEXX78vSLj5+LtO5dQyy_2rbbeg@mail.gmail.com
Whole thread Raw
In response to Re: Designing a better connection pool for psycopg3  (Magnus Hagander <magnus@hagander.net>)
Responses Re: Designing a better connection pool for psycopg3
Re: Designing a better connection pool for psycopg3
List psycopg
On Mon, 18 Jan 2021 at 15:39, Magnus Hagander <magnus@hagander.net> wrote:
>
> On Mon, Jan 18, 2021 at 3:29 PM Daniele Varrazzo
> <daniele.varrazzo@gmail.com> wrote:

> > I'm trying to imagine what happens in a case such as a network
> > partition or reconfiguration, and the app server doesn't see the
> > database anymore. This node is arguably broken.
>
> Only if this is the *only* thing it does.
>
> It might still be able to reach other services on other nodes. Other
> databases. Heck, even other database son the same node if it was a
> config error.

In your opinion (and Karsten's, if he'd like to chip in), what should
happen on program start? Is attempting to create a new connection in
the main thread, and throwing an exception if failing to do so, a
reasonable behaviour?

Cheers,

-- Daniele



psycopg by date:

Previous
From: Karsten Hilbert
Date:
Subject: Re: Designing a better connection pool for psycopg3
Next
From: Karsten Hilbert
Date:
Subject: Re: Designing a better connection pool for psycopg3