| From: | Paul Förster <paul(dot)foerster(at)gmail(dot)com> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | derwin theduck <hotchipsveg(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Could not resolve host name error in psycopg2 |
| Date: | 2020-04-17 07:02:26 |
| Message-ID: | EC756DEE-8C58-4F88-BA05-A9D7D3C3D15D@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi Adrian,
> On 17. Apr, 2020, at 03:00, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> wrote:
>
> Huh? Leaving open connections is not considered a good thing. In other words a connection should last for as long as it takes to get it's task done and then it should close.
I basically agree on this, but there are two big "but"s:
- recurring monitoring connections flood the logs unless they connect and never disconnect again.
- applications with hundreds or thousands of users may flood the logs, even though a pool may be used. If said pool doesn't keep its connections open most of the time you will notice that the database cluster is very busy logging connections.
Do you really want that?
Cheers,
Paul
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steve Atkins | 2020-04-17 08:13:08 | Re: Using unlogged tables for web sessions |
| Previous Message | Konireddy Rajashekar | 2020-04-17 06:38:58 | Pgbackrest restore options |