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

From Stephen Frost
Subject Re: Journal based VACUUM FULL
Date
Msg-id 20190222232121.GE6197@tamriel.snowman.net
Whole thread Raw
In response to Re: Journal based VACUUM FULL  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
List pgsql-hackers
Greetings,

* Andrew Dunstan (andrew.dunstan@2ndquadrant.com) wrote:
> On 2/22/19 2:15 PM, Andres Freund wrote:
> > 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.

Seems more appropriate to the developer unconference, though perhaps
that's what you meant..?

Thanks!

Stephen

Attachment

pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: Remove Deprecated Exclusive Backup Mode
Next
From: Michael Paquier
Date:
Subject: Re: Autovaccuum vs temp tables crash