| From: | Michael Banck <mbanck(at)gmx(dot)net> |
|---|---|
| To: | Antonin Houska <ah(at)cybertec(dot)at> |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Junwang Zhao <zhjwpku(at)gmail(dot)com>, Kirill Reshke <reshkekirill(at)gmail(dot)com>, 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: | 2025-01-30 08:34:01 |
| Message-ID: | 679b3979.5d0a0220.115578.3e08@mx.google.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On Mon, Jan 13, 2025 at 02:48:31PM +0100, Antonin Houska wrote:
> Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
> > On 2025-Jan-09, Antonin Houska wrote:
> > > It seems you accidentally fixed another problem :-) I was referring to the
> > > 'lockmode' argument of make_new_heap(). I can try to write a patch for that
> > > but ...
> > >
> > > > Meanwhile the patch 0004 has some seemingly trivial conflicts. If you
> > > > want to rebase, I'd appreciate that. In the meantime I'll give a look
> > > > at the next two other API changes.
>
> This is the patch series rebased on top of the commit cc811f92ba.
>
> I haven't addressed the problem of a new command yet - for that I'd like to
> see some sort of consensus, so that I do not have to do all the related
> changes many times.
Well, looks like this patch-set is blocked on the bikeshedding part?
Somebody should call a shot here, then.
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2025-01-30 08:36:32 | Re: Error in StrategySyncStart() prologue |
| Previous Message | Nazir Bilal Yavuz | 2025-01-30 08:02:15 | Re: BitmapHeapScan streaming read user and prelim refactoring |