Horton

Re: vacuumdb: permission denied for schema "pg_temp_7"

Michael Paquier <michael@paquier.xyz>

View thread
From: Michael Paquier <michael@paquier.xyz>
To: Fujii Masao <masao.fujii@oss.nttdata.com>
Cc: Christophe Pettus <xof@thebuild.com>, Nathan Bossart <nathandbossart@gmail.com>, vaibhave postgres <postgresvaibhave@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, Noah Misch <noah@leadboat.com>, pgsql-bugs@lists.postgresql.org, vsekar@microsoft.com
Date: 2024-09-24T23:10:16Z
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 Tue, Sep 24, 2024 at 11:20:43PM +0900, Fujii Masao wrote:
> On 2024/09/24 10:08, Michael Paquier wrote:
>> Somewhat missed this thread, thanks for the latest activity.
>> 
>> If we apply a restriction on the temporary persistence, then we know
>> that vacuumdb will always have a WHERE clause so we can simplify the
>> code and remove the business with has_where like in the attached.
> 
> LGTM.

Thanks.  As I am kind of behind this one, I'll go fix it first.  Let's
sort out the permission bits after that one is sorted out.  REL_17_0
is out, so this can happen across all branches.
--
Michael