| From: | Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net> |
|---|---|
| To: | psycopg(at)lists(dot)postgresql(dot)org, psycopg(at)postgresql(dot)org |
| Subject: | Re: Designing a better connection pool for psycopg3 |
| Date: | 2021-01-18 15:19:49 |
| Message-ID: | YAWnFSR2HIbR1hhM@hermes.hilbert.loc |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2021-01-18 15:20:18 | Re: Designing a better connection pool for psycopg3 |
| Previous Message | Daniele Varrazzo | 2021-01-18 15:12:05 | Re: Designing a better connection pool for psycopg3 |