Re: Journal based VACUUM FULL - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: Journal based VACUUM FULL
Date
Msg-id 26c0e9a8-930a-3172-cadb-205346eb0b95@2ndQuadrant.com
Whole thread Raw
In response to Re: Journal based VACUUM FULL  (Andres Freund <andres@anarazel.de>)
Responses Re: Journal based VACUUM FULL
List pgsql-hackers
On 2/22/19 2:15 PM, Andres Freund wrote:
> Hi,
>
> On 2019-02-21 16:27:06 +0100, Andreas Karlsson wrote:
>> I have not heard many requests for bringing back the old behavior, but I
>> could easily have missed them. Either way I do not think there would be much
>> demand for an in-place VACUUM FULL unless the index bloat problem is also
>> solved.
> Yea, I don't think there's much either. What I think there's PLENTY need
> for is something like pg_repack in core.  And could argue that the
> trigger based logging it does to catch up to changes made concurrently
> with the rewrite, to the old table, is a form of journaling...
>

+1. Maybe this is something that should be on the agenda of the next
developers' meeting.


cheers


andrew


-- 
Andrew Dunstan                https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Pluggable Storage - Andres's take
Next
From: Pavel Stehule
Date:
Subject: Re: proposal: variadic argument support for least, greatest function