Re: pg_stat_progress_create_index vs. parallel index builds - Mailing list pgsql-hackers

From Matthias van de Meent
Subject Re: pg_stat_progress_create_index vs. parallel index builds
Date
Msg-id CAEze2WgJ8qfOkvpQqDCNXww5WxXy5Y0qLafziJXPjA2SP2vCwA@mail.gmail.com
Whole thread Raw
In response to Re: pg_stat_progress_create_index vs. parallel index builds  (Tomas Vondra <tomas.vondra@enterprisedb.com>)
Responses Re: pg_stat_progress_create_index vs. parallel index builds
List pgsql-hackers
On Wed, 2 Jun 2021 at 17:42, Tomas Vondra <tomas.vondra@enterprisedb.com> wrote:
>
> On 6/2/21 4:54 PM, Matthias van de Meent wrote:
> > On Wed, 2 Jun 2021 at 15:23, Tomas Vondra <tomas.vondra@enterprisedb.com> wrote:
> >>
> >> ...
> >>
>  >
> > After looking at it a bit more, it seems like a solution was actually
> > easier than I'd expected. PFA a prototype (unvalidated, but
> > check-world -ed) patch that would add these subphases of progress
> > reporting, which can be backpatched down to 12.
> >
>
> Nice. I gave it a try on the database I'm experimenting with, and it
> seems to be working fine. Please add it to the next CF.

Thanks, cf available here: https://commitfest.postgresql.org/33/3149/

With regards,

Matthias van de Meent



pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: pg_stat_progress_create_index vs. parallel index builds
Next
From: John Naylor
Date:
Subject: speed up verifying UTF-8