Re: Fix DROP TABLESPACE on Windows with ProcSignalBarrier?

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Fix DROP TABLESPACE on Windows with ProcSignalBarrier?
Date: 2021-02-27 03:14:40
Message-ID: CA+hUKGKJKrVvsgOkivm6rnPPEhSFK+1VLjBcc8HXFRt46DeXZA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Here's a new version. The condition variable patch 0001 fixes a bug:
CleanupProcSignalState() also needs to broadcast. The hunk that
allows the interrupt handlers to use CVs while you're already waiting
on a CV is now in a separate patch 0002. I'm thinking of going ahead
and committing those two. The 0003 patch to achieve $SUBJECT needs
more discussion.

Attachment Content-Type Size
v4-0001-Use-condition-variables-for-ProcSignalBarriers.patch text/x-patch 4.0 KB
v4-0002-Allow-condition-variables-to-be-used-in-interrupt.patch text/x-patch 1.7 KB
v4-0003-Use-a-global-barrier-to-fix-DROP-TABLESPACE-on-Wi.patch text/x-patch 8.1 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2021-02-27 03:17:54 Re: [HACKERS] logical decoding of two-phase transactions
Previous Message Amit Kapila 2021-02-27 02:59:31 Re: repeated decoding of prepared transactions