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

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Mircea Cadariu <cadariu(dot)mircea(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: vacuumdb --analyze-only does not need to issue VACUUM (ONLY_DATABASE_STATS) ?
Date: 2025-09-16 15:36:45
Message-ID: CAHGQGwGCkMMLFHYjco5Z64uR38CVWiZrTgxUSJ5PZVceEMLdMQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Sep 16, 2025 at 10:06 PM Mircea Cadariu
<cadariu(dot)mircea(at)gmail(dot)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 Content-Type Size
v2-0001-vacuumdb-Do-not-run-VACUUM-ONLY_DATABASE_STATS-wh.patch application/octet-stream 2.0 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dmitry Mityugov 2025-09-16 15:47:18 Re: --with-llvm on 32-bit platforms?
Previous Message Tom Lane 2025-09-16 15:33:10 Re: Clarification on DROP OWNED BY command in PG18