| From: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de>, Andreas Karlsson <andreas(at)proxel(dot)se> |
| Cc: | Ryan David Sheasby <ryan27968(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Journal based VACUUM FULL |
| Date: | 2019-02-22 19:56:09 |
| Message-ID: | 26c0e9a8-930a-3172-cadb-205346eb0b95@2ndQuadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2019-02-22 19:57:53 | Re: proposal: variadic argument support for least, greatest function |
| Previous Message | Robert Haas | 2019-02-22 19:52:08 | Re: Pluggable Storage - Andres's take |