Re: why there is not VACUUM FULL CONCURRENTLY?

From: Michael Banck <mbanck(at)gmx(dot)net>
To: Kirill Reshke <reshkekirill(at)gmail(dot)com>
Cc: Antonin Houska <ah(at)cybertec(dot)at>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: why there is not VACUUM FULL CONCURRENTLY?
Date: 2024-07-22 09:53:58
Message-ID: 669e2c37.050a0220.7027a.20fe@mx.google.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jul 22, 2024 at 01:23:03PM +0500, Kirill Reshke wrote:
> Also, should we create a cf entry for this thread already?

I was wondering about this as well, but there is one for the upcoming
commitfest already:

https://commitfest.postgresql.org/49/5117/

Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Richard Guo 2024-07-22 09:55:47 Re: Possible incorrect row estimation for Gather paths
Previous Message Tomas Vondra 2024-07-22 09:46:20 Re: Make reorder buffer max_changes_in_memory adjustable?