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

From Karsten Hilbert
Subject Re: Designing a better connection pool for psycopg3
Date
Msg-id YAWnFSR2HIbR1hhM@hermes.hilbert.loc
Whole thread Raw
In response to Re: Designing a better connection pool for psycopg3  (Daniele Varrazzo <daniele.varrazzo@gmail.com>)
List psycopg
Am Mon, Jan 18, 2021 at 04:12:05PM +0100 schrieb Daniele Varrazzo:

> > > 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?

Sure ! The app can always catch that and decide what to do.

Karsten
--
GPG  40BE 5B0E C98E 1713 AFA6  5BC0 3BEA AC80 7D4F C89B



psycopg by date:

Previous
From: Daniele Varrazzo
Date:
Subject: Re: Designing a better connection pool for psycopg3
Next
From: Magnus Hagander
Date:
Subject: Re: Designing a better connection pool for psycopg3