On Mon, Sep 23, 2024 at 06:13:23PM -0700, Christophe Pettus wrote:
> One related but not identical thing that has come up with vacuumdb is
> that it terminates if it's not able to connect to any database that it
> finds in the initial query. This can happen if pg_hba.conf denies the
> user that is running vacuumdb access to a database that comes up during
> --all. Some hosting providers (in particular, Google) create restricted
> databases in the cluster that a customer role can't get access to. This
> pretty much defeats --analyze-in-stages. My suggested fix was to
> terminate with an error if the initial connection fails, but continue
> with a warning if further connections fail.
I think it'd be fine to continue with a warning when --all is used, but if
you specify a --dbname that you cannot connect to, then I think it should
fail.
--
nathan
