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 1s9owl-005M1F-JW for pgsql-general@arkaria.postgresql.org; Wed, 22 May 2024 16:36: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 1s9owk-001Fa7-3m for pgsql-general@arkaria.postgresql.org; Wed, 22 May 2024 16:36:10 +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 1s9owj-001FZx-M9 for pgsql-general@lists.postgresql.org; Wed, 22 May 2024 16:36:09 +0000 Received: from mail-ot1-x32f.google.com ([2607:f8b0:4864:20::32f]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1s9owd-001TkM-K1 for pgsql-general@postgresql.org; Wed, 22 May 2024 16:36:08 +0000 Received: by mail-ot1-x32f.google.com with SMTP id 46e09a7af769-6f0e7af802eso2426767a34.0 for ; Wed, 22 May 2024 09:36:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1716395762; x=1717000562; darn=postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=WS/dIGER/ah6LR4jzsBjnaisWLCDaTPYRHyiyznDhg0=; b=Wqk1dDi/TAi5lYWcDLCaa6WV4ce28RQG8KXJ/0HlzBU1CjU5pecKzgRdPsMzsPjCm7 q49KT9gUmvIzB3T6zhJRsa6onTcWphiF1V4XGLWf5dNuSfVMzVmxG3NqOAkVF7pqosSf L353Pf1U3Enk46w4nwAECCIpkNb0fLhrVnVkMF/q2x+ebMo/Cw02BXNdWmKfwUYHq9sB rjIW2SzPCODHVxUJalOlKj/nkHsP/L8lu8q4Iuwb/5VZQy39FuP35hetZ2hVWMyKGCOI dAmuH6XnFvswjBCWvTW+nQDw4lxb0g+vcknD3gkbQLTvooxvWMG9gBJDSjzYGGjb07ZQ V/nQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1716395762; x=1717000562; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=WS/dIGER/ah6LR4jzsBjnaisWLCDaTPYRHyiyznDhg0=; b=YoluqJ1K4Kyyu/RdXAPwTAIoo58aD4wsf22znozw3Iyr4R+/0ZG0YgmtLmt5WIBf2l TvYfWutdbiMwYHUishULWx0SGhItBrtQx1nmeigSuLsex7sjXI1tuKE8hzVvP98SjL38 P8OpnU9Iv8XQLxg/ds0vdtuyx/ESb9XRVgfAQUYoOxiqMexDXsn5kEKSZoreaqKh2aWH 9S+8GLXEHEX+ad/SMMr5mJjHUw5m99RCT0cl8wZtkVvj0w9vTEB4RJEWi9LdCzql+7tq FsuQDaoHBIJ1WdjXVGXdEeOFO9RV16FgACByezB0Vvhlgn8VdXL3dZ2N7aNWR6fRliDm s82w== X-Gm-Message-State: AOJu0YxS+PbDw6kaHImGzfANY/WTW6A24FY6Nkh9T3PM925TdhblU6Iv oNldbpn4iloTXbblrg/OBRW5QR7uvpmvwomoLpGdUPiz00MUu6ZXy1lGIQ3uyPeQzf7fPZjxJOq fymyAUxk87BQED9nHQgIiqoMnKKkfLvbk X-Google-Smtp-Source: AGHT+IHLM2IO1OQOZdcIXy4I/Kn1E9IkB34ES6hR3D0vrqHwnPl1FPFK2QAUL2dJ5gv+2HffXSBcSF/kfWP/5w1X7oo= X-Received: by 2002:a05:6870:c0c7:b0:240:7904:f5b6 with SMTP id 586e51a60fabf-24c68dfadeamr2555269fac.28.1716395762580; Wed, 22 May 2024 09:36:02 -0700 (PDT) MIME-Version: 1.0 From: Ron Johnson Date: Wed, 22 May 2024 12:35:51 -0400 Message-ID: Subject: search_path wildcard? To: pgsql-general Content-Type: multipart/alternative; boundary="000000000000b9040f06190d87c2" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000b9040f06190d87c2 Content-Type: text/plain; charset="UTF-8" This doesn't work, and I've found nothing similar: ALTER ROLE foo SET SEARCH_PATH = '*'; Is there a single SQL statement which will generate a search path based on information_schema.schemata, or do I have to write an anonymous DO procedure? SELECT schema_name FROM information_schema.schemata WHERE schema_name != 'information_schema' AND schema_name NOT LIKE 'pg_%'; --000000000000b9040f06190d87c2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
This doesn't work, and I've found nothing sim= ilar:
ALTER ROLE foo SET SEARCH_PATH=C2=A0 = =3D '*';

Is there a single SQL statement = which will generate a search path based on=C2=A0information_schema.schemata= , or do I have to write an anonymous DO procedure?
SELECT schema_name FROM information_schema.schemata WHERE schema= _name !=3D 'information_schema' AND schema_name NOT LIKE 'pg_%&= #39;;

--000000000000b9040f06190d87c2--