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 1s9qHy-005T9M-TE for pgsql-general@arkaria.postgresql.org; Wed, 22 May 2024 18:02:12 +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 1s9qHz-0026nW-0K for pgsql-general@arkaria.postgresql.org; Wed, 22 May 2024 18:02:11 +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 1s9qHy-0026nN-LS for pgsql-general@lists.postgresql.org; Wed, 22 May 2024 18:02:10 +0000 Received: from mail-pf1-x42d.google.com ([2607:f8b0:4864:20::42d]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1s9qHw-001USX-8N for pgsql-general@postgresql.org; Wed, 22 May 2024 18:02:09 +0000 Received: by mail-pf1-x42d.google.com with SMTP id d2e1a72fcca58-6f44d2b3130so2659986b3a.2 for ; Wed, 22 May 2024 11:02:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1716400927; x=1717005727; darn=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=jRsqZnjShia5uZ9RgOLH6QfzYO5+FZ5fNeKjdgiImAQ=; b=JFruoksQRMh3Xq0PH+QbBxRDSK/M0YqpHaTE85v/BbiBz4lqC0FIUsLJjrqTu9iHuc nzD82bqmdO6MWgysx+AYwbQztLlv2WF7TOilQU7UWJfToF7cXXdFv4QRglml7AYRlKo2 qP/aoIs7RZZi6HORGkqSRMNdJ7i6oLkjLW6pCn+ysA/BE0nZAiEiWcGwnHAZnqL+Abim /ATwT2obDwleP48OmfH/xfFE/ftxBejmxDrstqcX47BZ0HfOCPPPAp8Lx3gWQauFCIe8 14/IO2WnFrjl7s60x5vTV+4Az6GssX5moNlVYdK0QqtLa/rbVG95hDnap3oTRrViNDlb d0nw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1716400927; x=1717005727; 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=jRsqZnjShia5uZ9RgOLH6QfzYO5+FZ5fNeKjdgiImAQ=; b=E5tO0Ij+EfyJIXZ+omTpGYpDsaxGuLdu0yVxPR7H+a3/em/1hxh+5ZFywca4dvhrjU mBjQdU0SixjhkyUvh9mTgTtksnt/3Vs8dX2pQ6zSNl8eMvPcnIA+dD7Z4GOUtdOuKb11 XOs4s6AMCzpujmt8XaQjR7dNJU8UgoN/QBHQJYiuG7vazILPm6G/Ftkh51WLtUSEvpwZ lXvrHzNRw57fcMncNIM+ueMxgzvOyZx3/6/ustkVOaQETrA6VHfLvcxUZ0OwewlrdjOC jUI1BzWAb/0kquH6vQ21/6dAqk7QV718NisqWZtOALuN/MY+6H+BOLB3JaMClkCTXQrn m9hQ== X-Forwarded-Encrypted: i=1; AJvYcCXAAPDxg1TlgANGWCzO4NvNH9DD0KPwNxlzvqP/5DS40KrrsJHsmKJxL/qg5BI3PIFCOlCWc0hDfZQH9yPdO8cVsVGEFWxUfvvtgPeQ X-Gm-Message-State: AOJu0Yx+uMgq2vHn1tMn6D0gtj5rRBT45ke63heVBnVu/aNa5861zYFJ kugHgMayRPTK54DhvDCO51szUFjC0CyXNiZFMDtZPY0hTcYMTPpuwLDP3NjPOZ6yo8xKfA/0zR7 O0U3xWuZL+4zm4s6QxF377n2YtBo= X-Google-Smtp-Source: AGHT+IE1VEfHeIUXm/o2wpPZHuE/KZKAwLhlwcOWgU0lz/E4RD/Fw+IPRe/SoYosFFR3ihs+Xgomsgw4yUSc1T7L5nM= X-Received: by 2002:a05:6a21:3417:b0:1af:ac8a:19b1 with SMTP id adf61e73a8af0-1b1f8a4a004mr2903151637.50.1716400927267; Wed, 22 May 2024 11:02:07 -0700 (PDT) MIME-Version: 1.0 References: <4165841.1716397819@sss.pgh.pa.us> In-Reply-To: From: Isaac Morland Date: Wed, 22 May 2024 14:01:54 -0400 Message-ID: Subject: Re: search_path and SET ROLE To: Ron Johnson Cc: Tom Lane , pgsql-general Content-Type: multipart/alternative; boundary="0000000000008ff48506190ebb86" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000008ff48506190ebb86 Content-Type: text/plain; charset="UTF-8" On Wed, 22 May 2024 at 13:48, Ron Johnson wrote: As a superuser administrator, I need to be able to see ALL tables in ALL > schemas when running "\dt", not just the ones in "$user" and public. And I > need it to act consistently across all the systems. > \dt *.* But I am skeptical how often you really want this in a real database with more than a few tables. Surely \dn+ followed by \dt [schemaname].* for a few strategically chosen [schemaname] would be more useful? --0000000000008ff48506190ebb86 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Wed, 22 May 2024 at 13:48, Ron Johnson= <ronljohnsonjr@gmail.com= > wrote:

As a superuser admini= strator, I need to be able to see ALL tables in ALL schemas when running &q= uot;\dt", not just the ones in "$user" and public.=C2=A0 And= I need it to act consistently across all the systems.

\dt *.*

But I am ske= ptical how often you really want this in a real database with more than a f= ew tables. Surely \dn+ followed by \dt [schemaname].* for a few strategical= ly chosen [schemaname] would be more useful?
--0000000000008ff48506190ebb86--