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 1st6Yh-00Db6l-3p for pgsql-bugs@arkaria.postgresql.org; Tue, 24 Sep 2024 14:30:31 +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 1st6Yg-008gW3-EK for pgsql-bugs@arkaria.postgresql.org; Tue, 24 Sep 2024 14:30:30 +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 1st6Yg-008gVu-5T for pgsql-bugs@lists.postgresql.org; Tue, 24 Sep 2024 14:30:30 +0000 Received: from mail-io1-xd2e.google.com ([2607:f8b0:4864:20::d2e]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1st6YZ-000p2c-Ry for pgsql-bugs@lists.postgresql.org; Tue, 24 Sep 2024 14:30:28 +0000 Received: by mail-io1-xd2e.google.com with SMTP id ca18e2360f4ac-82ce1cd202cso319500139f.0 for ; Tue, 24 Sep 2024 07:30:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1727188223; x=1727793023; darn=lists.postgresql.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=3aGOCmH6wcFs9Heu7oKQI7PbLP2JkpF8B3KH99CNbjg=; b=DkFJNpfaWNXV6L1Ij3qkxOFqjEFeQ3XSx8CxMonkg2uWSVUYLcyoBcA2+IHS1FEtT9 1R2NSQtTc4Aej2gHEKzuF5vVZAuXb79yK9Bj7JuG12VVwJtbsikVnjKJOqis5X5rFaQU uszof+wfZohrg3ufql5GqZD49rNUzPL+0OVn1J4138e2sNefu3hQn9gjZAQdLxZ0XO7+ NWFe45LHrUtomZeCIiqhv78wlCQlEGL4IXP+bzhYfvsz3cPT0ZeMEhqiw0YbSLA+2mhY QXmo5Q7BzjWNHhQRrc+1IZFH8wRvUqgnuWG11P0Sn8UDthEZwJZyUxErai/aH77Oib08 0TWg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1727188223; x=1727793023; h=in-reply-to: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=3aGOCmH6wcFs9Heu7oKQI7PbLP2JkpF8B3KH99CNbjg=; b=l8deGjXzxbeu4G6/AZyP3vLFGhZCGZnmcD3orEXTeDxKtfUnFxSQCa4KPt6GZe6WNp bVT51Imvo0WkDm81rvFDDwnp75D/ja2l9fPcLU/Xf0qzhWSMwzsgTznog8ySj4nFrKiZ wglkxXEP5gtm964IR88TKG6C2IerlEitiyrcqjmFu2jYejpH53G61zwnbcQcvW/cSf// jfEyXgWDi1tJ0Q6xB/wFeHWE1lkPU2Cej5AgNc4icMfNqoCM7o1n/uXDFGqG7H5K2iid vBDw5GNVR3xjK2OTqP+2fP0oEOavoRZiaVNbZ8zImWtBOAfI+pSSGZ4kC+XGXdhik9F0 MD5w== X-Forwarded-Encrypted: i=1; AJvYcCUeye9fFGBHj7kvhenopO3JHwAgSD5Rfv74dYZp2QMPhgeqwMho1Wam1bD9b7ltdVRllOHwUCb2F1VR@lists.postgresql.org X-Gm-Message-State: AOJu0YwGEquBV/YrVmptSXb6zoKR7OY5OgWvj+7inVq9330Bv5f0HfIY IK0x44R0oG2qloES+WsnPMrqjfybwcuw7alWEGSmQe66pcujTggC X-Google-Smtp-Source: AGHT+IGi8bIseAquqZJ3+HDhcjH0P+HxDhKIyMZE5XF1tEZJtrNSGYcdsXUjtdYB6L1Y8CfWthSPWw== X-Received: by 2002:a05:6602:6427:b0:82d:1ba1:da5b with SMTP id ca18e2360f4ac-83209d7f2aemr1208079839f.13.1727188223042; Tue, 24 Sep 2024 07:30:23 -0700 (PDT) Received: from nathan (162-195-168-172.lightspeed.stlsmo.sbcglobal.net. [162.195.168.172]) by smtp.gmail.com with ESMTPSA id 8926c6da1cb9f-4d40f4120f8sm439630173.156.2024.09.24.07.30.22 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 24 Sep 2024 07:30:22 -0700 (PDT) Date: Tue, 24 Sep 2024 09:30:21 -0500 From: Nathan Bossart To: Christophe Pettus Cc: vaibhave postgres , Tom Lane , Fujii Masao , Noah Misch , PostgreSQL Bug List , vsekar@microsoft.com Subject: Re: vacuumdb: permission denied for schema "pg_temp_7" Message-ID: References: <20240920215030.8d.nmisch@google.com> <2603142.1726873660@sss.pgh.pa.us> <5f37ee56-14fb-44fe-9150-9eb97e10538b@oss.nttdata.com> <2649165.1726898595@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, Sep 23, 2024 at 06:13:23PM -0700, Christophe Pettus wrote: > One related but not identical thing that has come up with vacuumdb is > that it terminates if it's not able to connect to any database that it > finds in the initial query. This can happen if pg_hba.conf denies the > user that is running vacuumdb access to a database that comes up during > --all. Some hosting providers (in particular, Google) create restricted > databases in the cluster that a customer role can't get access to. This > pretty much defeats --analyze-in-stages. My suggested fix was to > terminate with an error if the initial connection fails, but continue > with a warning if further connections fail. 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. -- nathan