Re: Fix DROP TABLESPACE on Windows with ProcSignalBarrier?
Thomas Munro <thomas.munro@gmail.com>
From: Thomas Munro <thomas.munro@gmail.com>
To: Andres Freund <andres@anarazel.de>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2021-03-04T22:08:22Z
Lists: pgsql-hackers
On Thu, Mar 4, 2021 at 11:54 AM Thomas Munro <thomas.munro@gmail.com> wrote: > > I've been wondering what obscure hazards these "tombstone" (for want > > of a better word) files guard against, besides the one described in > > the comments for mdunlink(). I've been thinking about various > > schemes that can be summarised as "put the tombstones somewhere else", > > but first... this is probably a stupid question, but what would break > > if we just ... turned all this stuff off when wal_level is high enough > > (as it is by default)? The "how-to-make-it-so-that-we-don't-need-a-checkpoint" subtopic is hereby ejected from this thead, and moved over here: https://commitfest.postgresql.org/33/3030/
Commits
-
Fix DROP {DATABASE,TABLESPACE} on Windows.
- 4eb2176318d0 15.0 landed
-
Allow condition variables to be used in interrupt code.
- f5a5773a9dc4 14.0 landed
-
Use condition variables for ProcSignalBarriers.
- 814f1d8bc395 14.0 landed