Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1st6sr-00DdVk-Nk for pgsql-bugs@arkaria.postgresql.org; Tue, 24 Sep 2024 14:51:22 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1st6sq-00983P-Oi for pgsql-bugs@arkaria.postgresql.org; Tue, 24 Sep 2024 14:51:20 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1st6sq-00983H-GC for pgsql-bugs@lists.postgresql.org; Tue, 24 Sep 2024 14:51:20 +0000 Received: from mail-io1-xd2f.google.com ([2607:f8b0:4864:20::d2f]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1st6sn-000pPh-Aw for pgsql-bugs@lists.postgresql.org; Tue, 24 Sep 2024 14:51:19 +0000 Received: by mail-io1-xd2f.google.com with SMTP id ca18e2360f4ac-82aa3f65864so212028139f.2 for ; Tue, 24 Sep 2024 07:51:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1727189477; x=1727794277; darn=lists.postgresql.org; h=in-reply-to:content-transfer-encoding:content-disposition :mime-version:references:message-id:subject:cc:to:from:date:from:to :cc:subject:date:message-id:reply-to; bh=MBuZ76ISW/LFxnt9+On0aAzPjufjQprgBfrpBJPP7AA=; b=MKaEoYlVZMVSIypOLM1ludsRvELbX1woVn/a7adGBuhhqdC2evW1TtVHOVC6xqyNbr YtBfLR3vI4pDuK1D8YoeKsxrByOoDSRvU9zpkD5eJ6KJOCLmkPxHmcPaRQbUrSa04YUl +J4oWVoeX24pZvW9Pv5ZippHpD2gUFV/QYIn5ayUZ/Ptztrfb4lg/NRgcPa6s3cqj90n +Y+4wv/QwPW6vJb5cRahMRa2/D2QiqRRoZkfJAqde0F/eUF6zfpogbUuguME5w2vGXo+ qJCma42W76QH1Xkx+DZ45CWlFBfOaUKxq+V9fXttx3t3qRtBLb5h786i85DyjfX2kB9o ddzg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1727189477; x=1727794277; h=in-reply-to:content-transfer-encoding:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=MBuZ76ISW/LFxnt9+On0aAzPjufjQprgBfrpBJPP7AA=; b=Lks6fM0nPAGFKvjcCXuxtvr/Oih74FpV+W4lNwl24lr+CMuu4uaA14J7UtL1H5OSGv vKyU89pf9ijQqq1USZ8MIwxUXUI/2rTR2CMeXWHxNlmFOUtn29ipkYuuufkNJqq8RGfe XeeSnAeh/ffLXNj7CkmPDBH0XPGUbRR7x7OW/d0ajnD6hfL6/ZOXcMDAQSJGEu5D4hMG eN6nkStLSOmM9G7kM5k/ZyONTS6lYtDnJNNhVKzwvQVC/vCbwB1rBamEjZeFYOk2qs4n sIyHOCXSebEA0GSiSyZ9TOnEviZJHuv63dUBFpoBBQ5rvWE7UcR9B5ID1Ul+Rm6Hl7Lt RDKg== X-Forwarded-Encrypted: i=1; AJvYcCXGdfLJeQIbAwQvX5wb448O6leAChyTiVfADiCSVjir3eT5lSg7K9dRvoQWvi2iF83ObNBUweTR6rO9@lists.postgresql.org X-Gm-Message-State: AOJu0YxztmFYNzZzqOwV3zv9X9XZRzjtTh7ymnb7mELvjSl8Mf5CFPr9 /miR+giCQZ6khdflJquvzNim0hLXHkFnWBaiDNkHITql+p8SCEde X-Google-Smtp-Source: AGHT+IEBXwJDJIos/BH3wHDHs9525ol/On1tnsr2217HUBwcbaxe47MkuzUyyxWSK4sMiLlC7bEuCQ== X-Received: by 2002:a05:6602:1589:b0:82a:a4e7:5544 with SMTP id ca18e2360f4ac-83209d479d3mr1283360339f.9.1727189476584; Tue, 24 Sep 2024 07:51:16 -0700 (PDT) Received: from nathan (162-195-168-172.lightspeed.stlsmo.sbcglobal.net. [162.195.168.172]) by smtp.gmail.com with ESMTPSA id ca18e2360f4ac-8323f5f9e58sm45662339f.32.2024.09.24.07.51.15 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 24 Sep 2024 07:51:16 -0700 (PDT) Date: Tue, 24 Sep 2024 09:51:14 -0500 From: Nathan Bossart To: Fujii Masao Cc: Michael Paquier , Christophe Pettus , vaibhave postgres , Tom Lane , Noah Misch , pgsql-bugs@lists.postgresql.org, vsekar@microsoft.com Subject: Re: vacuumdb: permission denied for schema "pg_temp_7" Message-ID: References: <2603142.1726873660@sss.pgh.pa.us> <5f37ee56-14fb-44fe-9150-9eb97e10538b@oss.nttdata.com> <2649165.1726898595@sss.pgh.pa.us> <00d98a9f-bec1-4cd0-b59e-1043ae04c8bc@oss.nttdata.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, Sep 24, 2024 at 11:49:12PM +0900, Fujii Masao wrote: > On 2024/09/24 23:26, Nathan Bossart wrote: >> Yeah, this is what I mentioned upthread [0]. If the user doesn't specify >> anything in --table or --schema, then it's probably fine to silently skip >> objects for which they lack privileges. But if they do explicitly specify >> a table or schema that they cannot vacuum, then IMHO it'd be better to >> fail. > > This could be debatable. To be honest, if I run something like vacuumdb mydb, > *I* expect all eligible tables in that database to be vacuumed. If I forget to > grant the necessary privileges to the role, IŽd prefer to see errors from > vacuumdb so I can fix the permissions. > > If we decide to skip tables without enough privilege, IŽd prefer adding > an option like --skip-unprivileged-tables rather than changing the default behavior. I'm okay with that approach. -- nathan