Message-ID: <059dfcc2-81fd-4936-8d92-099490c0c713@oss.nttdata.com>
Date: Sat, 21 Sep 2024 14:56:22 +0900
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: vacuumdb: permission denied for schema "pg_temp_7"
Content-Language: en-US
To: Noah Misch <noah@leadboat.com>,
 vaibhave postgres <postgresvaibhave@gmail.com>, nathandbossart@gmail.com
Cc: pgsql-bugs@lists.postgresql.org, vsekar@microsoft.com
References: 
 <CAM_eQjwfAR=y3G1fGyS1U9FTmc+FyJm9amNfY2QCZBnDDbNPZg@mail.gmail.com>
 <20240920190731.37.nmisch@google.com>
From: Fujii Masao <masao.fujii@oss.nttdata.com>
In-Reply-To: <20240920190731.37.nmisch@google.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/059dfcc2-81fd-4936-8d92-099490c0c713%40oss.nttdata.com>
Precedence: bulk


On 2024/09/21 4:07, Noah Misch wrote:
> Non-superuser vacuumdb
> must be rare indeed for this to go unnoticed long enough to leave all
> supported branches affected.

Yes.
And more users might notice this in v17 or later, since v17 supports
the maintain privilege. Some users may want to use a role with
the maintain privilege to run vacuumdb. If they forget to grant USAGE
privilege on the temp table's schema to that role, they'll encounter
the same issue.

Regards,

-- 
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION