From: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
---|---|
To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Use WaitLatch for {pre, post}_auth_delay instead of pg_usleep |
Date: | 2021-07-12 15:56:19 |
Message-ID: | CALj2ACV6W-oeSUfEU38+pPu+cijknuUVCFV1psqSL5=bfpu3ZQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
As suggested in [1], starting a new thread for discussing $subject
separately. {pre, post}_auth_delay waiting logic currently uses
pg_usleep which can't detect postmaster death. So, there are chances
that some of the backends still stay in the system even when a
postmaster crashes (for whatever reasons it may be). Please have a
look at the attached patch that does $subject. I pulled out some of
the comments from the other thread related to the $subject, [2], [3],
[4], [5].
[1] - https://www.postgresql.org/message-id/YOv8Yxd5zrbr3k%2BH%40paquier.xyz
[2] - https://www.postgresql.org/message-id/162764.1624892517%40sss.pgh.pa.us
[3] - https://www.postgresql.org/message-id/20210705.145251.462698229911576780.horikyota.ntt%40gmail.com
[4] - https://www.postgresql.org/message-id/flat/20210705155553.GD20766%40tamriel.snowman.net
[5] - https://www.postgresql.org/message-id/YOOnlP4NtWVzfsyb%40paquier.xyz
Regards,
Bharath Rupireddy.
Attachment | Content-Type | Size |
---|---|---|
v1-0001-Use-a-WaitLatch-for-Pre-and-Post-Auth-Delay.patch | application/octet-stream | 7.4 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2021-07-12 16:10:24 | Re: Is tuplesort meant to support bounded datum sorts? |
Previous Message | Fujii Masao | 2021-07-12 15:49:58 | Re: Inaccurate error message when set fdw batch_size to 0 |