Re: vacuumdb: permission denied for schema "pg_temp_7"

From: Christophe Pettus <xof(at)thebuild(dot)com>
To: Nathan Bossart <nathandbossart(at)gmail(dot)com>
Cc: vaibhave postgres <postgresvaibhave(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, PostgreSQL Bug List <pgsql-bugs(at)lists(dot)postgresql(dot)org>, vsekar(at)microsoft(dot)com
Subject: Re: vacuumdb: permission denied for schema "pg_temp_7"
Date: 2024-09-24 15:22:32
Message-ID: 8F7C7040-1163-440E-9182-53AF34C606D4@thebuild.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> On Sep 24, 2024, at 07:30, Nathan Bossart <nathandbossart(at)gmail(dot)com> wrote:
> 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.

Yes, that's essentially my proposal. If --all is not specified, or if it cannot make the initial connection to determine which databases are in the instance, it stops with a fatal error just as it does now.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Laurenz Albe 2024-09-24 15:45:14 Re: Using a lot of memory in each session.
Previous Message Nathan Bossart 2024-09-24 14:51:14 Re: vacuumdb: permission denied for schema "pg_temp_7"