| From: | Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Another WaitEventSet resource leakage in back branches |
| Date: | 2024-04-05 10:55:16 |
| Message-ID: | CAPmGK15KRHgwf=5Gfsv_0WYjK87ajH7=SqVmCfsoL7VhT5k+JQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Mar 22, 2024 at 9:15 PM Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com> wrote:
> While working on [1], I noticed $SUBJECT: WaitLatchOrSocket in back
> branches is ignoring the possibility of failing partway through, too.
> I added a PG_FAINALLY block to that function, like commit 555276f85.
> Patch attached.
I noticed that PG_FAINALLY was added in v13. I created a separate
patch for v12 using PG_CATCH instead. Patch attached. I am attaching
the previous patch for later versions as well.
I am planning to back-patch these next week.
Best regards,
Etsuro Fujita
| Attachment | Content-Type | Size |
|---|---|---|
| fix-another-WaitEventSet-resource-leakage.patch | application/octet-stream | 2.6 KB |
| fix-another-WaitEventSet-resource-leakage-PG12.patch | application/octet-stream | 2.6 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bertrand Drouvot | 2024-04-05 11:01:50 | Re: Synchronizing slots from primary to standby |
| Previous Message | Andrey M. Borodin | 2024-04-05 10:49:24 | Re: CSN snapshots in hot standby |