Request a Demo
Home   >   mailing lists

Re: pg_stat_progress_cluster: do not default to CLUSTER - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: pg_stat_progress_cluster: do not default to CLUSTER
Date
Msg-id CAHGQGwH6rAd+fxWKRw=-i+SbzFtFRGDA5VBGJdMNNEsPO9YTqg@mail.gmail.com
Whole thread
Responses Re: Batching in executor
List pgsql-hackers
Tree view 
On Thu, Sep 3, 2026 at 7:39 PM Zsolt Parragi <zsolt.parragi@percona.com> wrote:
> The attached patch fixes this to report NULL instead.

Thanks for the patch! It looks good to me. So, barring any objections,
I'll commit it.

BTW, as a separate issue, is the following also problematic?

    WHEN command = 'REPACK' AND repack_index_relid = 0 THEN 'VACUUM FULL'

REPACK ... USING INDEX ... should basically be displayed as "CLUSTER".
But, if an index scan is not used (for example, when
enable_indexscan is disabled), repack_index_relid can be 0, causing
it to be displayed as "VACUUM FULL" unexpectedly. Thoughts?

Regards,

--
Fujii Masao
Attachment

pgsql-hackers by date:

Previous
From: Sami Imseih
Date:
Subject: Improve WAIT FOR read-your-writes consistency doc
Next
From: Michael Paquier
Date:
Subject: Re: DSA_ALLOC_NO_OOM vs dsm_create ERROR leaving a half-initialized pgstats hash entry