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 1s9rk8-005dyn-Lw for pgsql-general@arkaria.postgresql.org; Wed, 22 May 2024 19:35: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 1s9rk8-002zA2-5k for pgsql-general@arkaria.postgresql.org; Wed, 22 May 2024 19:35: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 1s9rk7-002z9u-Qu for pgsql-general@lists.postgresql.org; Wed, 22 May 2024 19:35:19 +0000 Received: from mail-yb1-xb30.google.com ([2607:f8b0:4864:20::b30]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1s9rk4-001V4c-R7 for pgsql-general@postgresql.org; Wed, 22 May 2024 19:35:18 +0000 Received: by mail-yb1-xb30.google.com with SMTP id 3f1490d57ef6-df4e1366da6so1327888276.1 for ; Wed, 22 May 2024 12:35:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1716406516; x=1717011316; 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=iOvHsUltciENpN9h63s6f6CjKzAhcZCvZsmUWuxTIE8=; b=QQrx6fVCzezsoPr0PwJTkdD8uYWmgwonk5BN8nD7eq7fjZIPLdYXWdT3yl+s7/B5xb 7rYH+EE9hw16hCtm6fOh3gbo3tXbtjuyEJYM/2gLULuY0I8OUbTaa3TliEDL1whRjOzF UXA2zWqjAVzFexnU0QhexGsDIJDfN3fUsmDp0/ZD0krVW2eAufnQskxP4OrD/qOv4mT4 MJcsmkKqiOfZMNCQdTpQtw5S/X7kEmqpQDjTfdLixBL2LvsX6IeKyVG9BSqbLKhnP/eP q+WG3SHqyzGHv1RDsxz3O3i0bwUYfM69pwrgEJNCssO48zW4AL2vbH3zhrWDOpSd9PBb FvRA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1716406516; x=1717011316; 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=iOvHsUltciENpN9h63s6f6CjKzAhcZCvZsmUWuxTIE8=; b=YjTnFRIBWu0y0G2hpCmqnISYJVu0Us03BDdH/Rj/oDbdTukaqXaj5qoFuL409DcDKu QVaHwsWF+6nadxf6g+6cF76/1IHSLk8nX/zl7A7U9iQOUiMm6IAWZFO8Flpku3Av2LPU 5z856A1+FmJtft85Oiab2Nzu5R8bAahxzemLPfDU7cdqy0651E70oANIcs4ZkXbrbCOf 6oumywzbQvxrfz8aOscEdJMG7laydLeVvgSMKRQBM/uYMuEQRc/ZnTDqgZHf4W8qoLRv tcF+prTxrZpmHxAm6rkInnQRzK3jq4i7VSWf0IYwCd+7brn2saDAgczHb6A90LMfvXgX +UYQ== X-Gm-Message-State: AOJu0YxszEdt44p5DHMBSZwxnXGOx6T6zsAELXzuLwvdxaPusUkFkeiX DRzwOPyKoSocNXFf6rvMkyThF5igDr6oyJAh/S5bnEVJDvaVjAw1U+/4impwuYWYlnNNz58OtzV TwRBf69HZlIQLVGp99+cNgRrd3vhZwQ== X-Google-Smtp-Source: AGHT+IH2aNi/SirELZazK2cHbr1tqH8pxjnhPT02enN8TZ1x4T8UZDZ2m8YtsQ/CijaIPcV7jFsuXm3jnPxV/6E6+VY= X-Received: by 2002:a25:ac04:0:b0:de5:6a2f:45d3 with SMTP id 3f1490d57ef6-df4e0d9b66bmr4614514276.36.1716406516101; Wed, 22 May 2024 12:35:16 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Pavel Stehule Date: Wed, 22 May 2024 21:34:39 +0200 Message-ID: Subject: Re: search_path wildcard? To: Ron Johnson Cc: pgsql-general Content-Type: multipart/alternative; boundary="000000000000aebc23061910085b" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000aebc23061910085b Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable st 22. 5. 2024 v 19:54 odes=C3=ADlatel Ron Johnson napsal: > On Wed, May 22, 2024 at 12:53=E2=80=AFPM David G. Johnston < > david.g.johnston@gmail.com> wrote: > >> On Wed, May 22, 2024, 10:36 Ron Johnson wrote: >> >>> This doesn't work, and I've found nothing similar: >>> ALTER ROLE foo SET SEARCH_PATH =3D '*'; >>> >> >> Correct, you cannot do that. >> > > That would be a helpful feature for administrators, when there are > multiple schemas in multiple databases, on multiple servers: superusers g= et ALTER > ROLE foo SET SEARCH_PATH =3D '*'; and they're done with it. > It can be pretty dangerous, because you don't specify order of schemas Regards Pavel --000000000000aebc23061910085b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

--000000000000aebc23061910085b--