Re: vacuumdb: permission denied for schema "pg_temp_7"

Christophe Pettus <xof@thebuild.com>

From: Christophe Pettus <xof@thebuild.com>
To: Nathan Bossart <nathandbossart@gmail.com>
Cc: vaibhave postgres <postgresvaibhave@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, Fujii Masao <masao.fujii@oss.nttdata.com>, Noah Misch <noah@leadboat.com>, PostgreSQL Bug List <pgsql-bugs@lists.postgresql.org>, vsekar@microsoft.com
Date: 2024-09-24T15:22:32Z
Lists: pgsql-bugs

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. vacuumdb: Schema-qualify operator in catalog query's WHERE clause.

  2. reindexdb: Skip reindexing temporary tables and indexes.

  3. vacuumdb: Skip temporary tables in query to build list of relations

  4. Use catalog query to discover tables to process in vacuumdb


> On Sep 24, 2024, at 07:30, Nathan Bossart <nathandbossart@gmail.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.