| From: | Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net> |
|---|---|
| To: | Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com> |
| Cc: | psycopg(at)postgresql(dot)org |
| Subject: | Re: Designing a better connection pool for psycopg3 |
| Date: | 2021-01-18 14:19:44 |
| Message-ID: | YAWZAK9keRiSHaRs@hermes.hilbert.loc |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | psycopg |
Am Mon, Jan 18, 2021 at 02:50:34PM +0100 schrieb Daniele Varrazzo:
> > I would strongly advise against making sys.exit() the default
> > for pool.terminate() unless I misunderstand something.
>
> How would you terminate the program if a maintenance thread, not the
> main one, thinks that the program is not in working state?
To me it is not the business of a library to terminate its
user (eg an application) upon resource starvation. After all,
the app may be perfectly fine with not being able to talk to
the database. Only it knows what to do under such
circumstances.
If one wants to support such machinery, I would suggest a
callback into the application, set up by the application
code.
Karsten
--
GPG 40BE 5B0E C98E 1713 AFA6 5BC0 3BEA AC80 7D4F C89B
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniele Varrazzo | 2021-01-18 14:29:34 | Re: Designing a better connection pool for psycopg3 |
| Previous Message | Karsten Hilbert | 2021-01-18 14:15:55 | Re: Designing a better connection pool for psycopg3 |