Re: vacuumdb --analyze-only does not need to issue VACUUM (ONLY_DATABASE_STATS) ? - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: vacuumdb --analyze-only does not need to issue VACUUM (ONLY_DATABASE_STATS) ?
Date
Msg-id CAHGQGwGCkMMLFHYjco5Z64uR38CVWiZrTgxUSJ5PZVceEMLdMQ@mail.gmail.com
Whole thread Raw
In response to Re: vacuumdb --analyze-only does not need to issue VACUUM (ONLY_DATABASE_STATS) ?  (Mircea Cadariu <cadariu.mircea@gmail.com>)
List pgsql-hackers
On Tue, Sep 16, 2025 at 10:06 PM Mircea Cadariu
<cadariu.mircea@gmail.com> wrote:
>
> The following review has been posted through the commitfest application:
> make installcheck-world:  tested, passed
> Implements feature:       tested, passed
> Spec compliant:           tested, passed
> Documentation:            tested, passed
>
> Hi,
>
> I tested the patch with log_statement = 'all' and I confirm I do not see the VACUUM log line anymore.

Thanks for the review and testing!


> You could consider adding the following representative test in src/bin/scripts/t/100_vacuumdb.pl:
> $node->issues_sql_unlike(
>     [ 'vacuumdb', '--analyze-only', 'postgres' ],
>     qr/statement: VACUUM.*;/,
>     'vacuumdb --analyze-only skips vacuum');

+1. I've added that test to the patch.
Attached is the updated version of the patch.

Regards,

--
Fujii Masao

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Clarification on DROP OWNED BY command in PG18
Next
From: Dmitry Mityugov
Date:
Subject: Re: --with-llvm on 32-bit platforms?