| 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 14:46:49 |
| Message-ID: | 825EEE0F-7923-48B7-8CC3-5FCE7E6F7750@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi Adrian,
> On 17. Apr, 2020, at 16:10, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> wrote:
>
> But most pools can grow and shrink in response to demand, so at some point there are connect/disconnect cycles.
yes, but it is a difference whether you see occasional growing and shrinking pool behavior, or the logs are flooded with connect/disconnect messages by short client connects. A relatively small number of connect/disconnect messages coming from a pool is mostly acceptable while huge numbers are not.
And as for monitoring applications, I would be a big fan of a parameter like log_exclude_users='user1,user2,...' to list usernames who should not appear in log files.
Cheers,
Paul
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sonam Sharma | 2020-04-17 14:47:02 | Re: Replication issue |
| Previous Message | Julien Rouhaud | 2020-04-17 14:45:29 | Re: Replication issue |