Re: Designing a better connection pool for psycopg3

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 14:42:46
Message-ID: YAWeZsmLydefv+Uu@hermes.hilbert.loc
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: psycopg

Am Mon, Jan 18, 2021 at 03:29:34PM +0100 schrieb Daniele Varrazzo:

> Anyway I appreciate that the default of terminating a program is
> probably too aggressive. So I would remove the `terminate()` function
> and base implementation and leave a `connection_failed()` handler,
> with a default no-op implementation, which people preferring their
> program to terminate can subclass (with `sys.exit(1)` or whatever
> termination strategy they find useful).

+1

Some apps may just gladly carry on buffering data locally,
and sending them to the backend next time they get a chance
to do so.

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

In response to

Browse psycopg by date

  From Date Subject
Next Message Daniele Varrazzo 2021-01-18 14:43:54 Re: Designing a better connection pool for psycopg3
Previous Message Magnus Hagander 2021-01-18 14:39:20 Re: Designing a better connection pool for psycopg3