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 1sokGa-00DVQK-2W for pgsql-general@arkaria.postgresql.org; Thu, 12 Sep 2024 13:53:49 +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 1sokGZ-008mIP-Au for pgsql-general@arkaria.postgresql.org; Thu, 12 Sep 2024 13:53:47 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sokGY-008mIG-W5 for pgsql-general@lists.postgresql.org; Thu, 12 Sep 2024 13:53:46 +0000 Received: from mail-lj1-x230.google.com ([2a00:1450:4864:20::230]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sokGR-000pNJ-Fs for pgsql-general@lists.postgresql.org; Thu, 12 Sep 2024 13:53:46 +0000 Received: by mail-lj1-x230.google.com with SMTP id 38308e7fff4ca-2f75de9a503so11613351fa.0 for ; Thu, 12 Sep 2024 06:53:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1726149220; x=1726754020; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=vWqKLMywlIDdHAmrvB+sMokECZT69FkJqQnGUTN79mM=; b=Ll+OvjzXBUnv0j2b1dux/+at7FYP7uagATH5mCje4lYwbkQ6yGY7T24GJdt0P5iDoU +t5BRCn/22A0pOYt8fFDOWVe8t+LAiIerPnL08BsWZ9s8+o9iAm/Zn30sL83uUazytOO Hne/pIXQALH4OcWZoaKHzMV1XW4LVgy1Odqbtle5a9rCXCpvgLNSgR4Fk3olnY0ZBZ78 wTcwquEDdgwzpNPEBHW3Z8I/xhedMNqVYH149k6PctXvpsTJukvimfRH74mv6NnuthAe v+iHWO5XdD8OdSEPMli/vorkHRMbUTcR9n7qGrALRbsF9ZtTlaRqoV+JTIHXWkUE1xpB 6Qnw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1726149220; x=1726754020; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=vWqKLMywlIDdHAmrvB+sMokECZT69FkJqQnGUTN79mM=; b=qVUKcMgJVx3TRAlDgetUm7Ik2mn+Qtp0RJ2gHjzbm7K7Bfka3HQfC6Pf6NNYOYeDUS PgQFNVjzQPCF2JA1juudBaXE36Sbs5GrFUbxwHTEkM2g3MOaw0dfrlEx2Lq25ntXnyWE Oxp1aA9TGG0+q0+O1F9SNwFbxHCUtsKL7U+2CT4x2Jo0CiTd2I/2qQJEdTJvW4CJCm5r 9E7TX5PjfNEbfdLQeYEveukD0UeLP/OWMHDk3t5QjLVuG6pW7rrKqw0F5R8e4BQDUaiO RUR4Pmz+Vblf0us7r/2QHJqglz0QZlW6HZ62dmhnaE4DbISMbR/e28lPwaS6dk7bg+VE wjlA== X-Forwarded-Encrypted: i=1; AJvYcCUdMxafdVeTYEvJpTbiJWB2guDvtG27MBoo+riurZ/MOB23BmoA/PPrQkzW+KAhsqABN1wWglzLLgxfKNZW@lists.postgresql.org X-Gm-Message-State: AOJu0YyCWqhztWC3LbMNdH/CDdkBTz8uSp9qQaOjDEHOIqMZdfGfWGCY 5DGUNYqnxiK3347oPcZ7CSyscOVfpKRApRDnRzfOB9/UsC6y9wgGf30ixg9LuX9FL5Vcv6ym2+4 92CF3eNqHhJuzP7jGuAKRi40yHzs= X-Google-Smtp-Source: AGHT+IEissgn6DkdGpVHq9hz5mdAJrjQbSVv0MKW7MAHN6K+RYxPST9qEaFgq3ewnvq881RjXlXLI3uC0jVYtGjwGAs= X-Received: by 2002:a05:651c:220c:b0:2f7:5519:710d with SMTP id 38308e7fff4ca-2f787f447dfmr17894631fa.33.1726149218965; Thu, 12 Sep 2024 06:53:38 -0700 (PDT) MIME-Version: 1.0 References: <3952715.1726115805@sss.pgh.pa.us> In-Reply-To: From: Greg Sabino Mullane Date: Thu, 12 Sep 2024 09:53:02 -0400 Message-ID: Subject: Re: Effects of REVOKE SELECT ON ALL TABLES IN SCHEMA pg_catalog FROM PUBLIC To: Dominique Devienne Cc: Andreas Joseph Krogh , Tom Lane , pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="00000000000006a2770621ec6f3f" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000006a2770621ec6f3f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Sep 12, 2024 at 9:12=E2=80=AFAM Dominique Devienne wrote: > On Thu, Sep 12, 2024 at 3:06=E2=80=AFPM Greg Sabino Mullane > wrote: > > (Also note that determining if a database or user exists does not even > require a successful login to the cluster.) > > Hi. How so? I was not aware of such possibilities. > Can you please give pointers (docs, examples) of this? > $ psql -U eve psql: error: connection to server on socket "/tmp/.s.PGSQL.5432" failed: FATAL: role "eve" does not exist $ psql -U postgres -d theater psql: error: connection to server on socket "/tmp/.s.PGSQL.5432" failed: FATAL: database "theater" does not exist $ psql -U alice -d template1 psql: error: connection to server on socket "/tmp/.s.PGSQL.5432" failed: FATAL: password authentication failed for user "alice" Cheers, Greg --00000000000006a2770621ec6f3f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Thu, Sep 12, 2024 at 9:12=E2=80=AFAM D= ominique Devienne <ddevienne@gmai= l.com> wrote:
On Thu, Sep 12, 2024 at 3:06=E2=80=AFPM Gr= eg Sabino Mullane <htamfids@gmail.com> wrote:
> (Also note that determining if a database or user exists does not even= require a successful login to the cluster.)

Hi. How so? I was not aware of such possibilities.
Can you please give pointers (docs, examples) of this?

$ psql -U eve
psql: error: connection to serv= er on socket "/tmp/.s.PGSQL.5432" failed: FATAL: =C2=A0role "= ;eve" does not exist

$ psql -U postgres -d theaterpsql: error: connection to server on socket "/tmp/.s.PGSQL.5432"= ; failed: FATAL: =C2=A0database "theater" does not exist=C2=A0

$ psql -U alice -d template1
psql: err= or: connection to server on socket "/tmp/.s.PGSQL.5432" failed: F= ATAL: =C2=A0password authentication failed for user "alice"

Cheers,
Greg

--00000000000006a2770621ec6f3f--