Re: Lock-free compaction. Why not? - Mailing list pgsql-hackers

From Michael Banck
Subject Re: Lock-free compaction. Why not?
Date
Msg-id 669e53c2.050a0220.387ed3.7669@mx.google.com
Whole thread Raw
In response to Re: Lock-free compaction. Why not?  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Lock-free compaction. Why not?
List pgsql-hackers
Hi,

On Mon, Jul 22, 2024 at 08:39:23AM -0400, Robert Haas wrote:
> What the extensions that are out there seem to do is, as I understand
> it, an online table rewrite with concurrent change capture, and then
> you apply the changes to the output table afterward. That has the
> problem that if the changes are happening faster than you can apply
> them, the operation does not terminate. But, enough people seem to be
> happy with this kind of solution that we should perhaps look harder at
> doing something along these lines in core.

I believe this is being discussed here:

https://commitfest.postgresql.org/49/5117/
https://www.postgresql.org/message-id/5186.1706694913%40antos


Michael



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Lock-free compaction. Why not?
Next
From: Joe Conway
Date:
Subject: Re: CI, macports, darwin version problems