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 1tD9I5-00GJI0-Gs for pgsql-general@arkaria.postgresql.org; Mon, 18 Nov 2024 21:28:13 +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 1tD9I2-007vXo-Rp for pgsql-general@arkaria.postgresql.org; Mon, 18 Nov 2024 21:28:11 +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 1tD9I2-007vXg-GZ for pgsql-general@lists.postgresql.org; Mon, 18 Nov 2024 21:28:11 +0000 Received: from mail-oi1-x22b.google.com ([2607:f8b0:4864:20::22b]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tD9I0-002dPz-2g for pgsql-general@lists.postgresql.org; Mon, 18 Nov 2024 21:28:10 +0000 Received: by mail-oi1-x22b.google.com with SMTP id 5614622812f47-3e6359ab118so2806553b6e.1 for ; Mon, 18 Nov 2024 13:28:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1731965286; x=1732570086; 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=PGB2RpvJx5ofJ7luHCSOIEdyO4RcrLtAZI1dWrq73Vw=; b=aDGLmlm9iDegulD3Y4RkgkOjn2ek4XFabtheAvdDAxVmcGYYbyw27WrIrdspFJaxMi IJoM8nO0pQ7KQU1YpoaMniQ0EmqtAtixTmUEHpyk2L59l4yN5k89aetWaEwvKERgXjKQ qDFBXymg/V2KVK0htTZ6tcuxWEcRglbYLiuQjRUXT383DUgNiwcJDZcLeNdWbkazZPiu 4oyQhHPn1XliVbdZVJYCOF9I/aJY1/cMEl1sAst3Rx94GUY0oQUQ7b3Mtvxcd62KT/E0 RVagF+CW+wUZquyoj1kbPLJaqt5GBF7srQ0RjSvKPmGPTtmTFC/8TSjUPJTB3iFAWFbg 7CxQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1731965286; x=1732570086; 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=PGB2RpvJx5ofJ7luHCSOIEdyO4RcrLtAZI1dWrq73Vw=; b=R9vK3/oDx0I5usfRjS0lTeVAk8AqPUjTCMrQHbivFfYUQ94+BsL2XUTwBL9E/lPJmY g5SS6ShzbGHr/jt7awvQrlMgmsc/pFySlnt+4plKbD4K5S98B4e/uLgHis35IXie4s9s NHZizoa9FENrTn+D5uGh7MdHLCrT6UVjHhhIDlZKIbnwmuBMGZ9V9XqjvTh6qyWb2hdT or6fZMFQhyjFH0d+2g/QzanEbFvtGDWfO40k+/MWU2HK/ArEc78t6pbdVzojQg5duUZV MW51tJNxypWQWnSKuaXcHeKNk5825MjLwRHIotwcjNxENEV7r/BYWQNWg4wAqG70OOLD zzqg== X-Gm-Message-State: AOJu0Yzo5+QdPNdaqIpkBL3/Y+vxwftKwUuiazFK9ydHVYR9n8eQZqZV y15vaY8jHofW2+V6eUHq2Rzn49/y+tdsR4sbpAIEiC5Imb08sOWnKwvBnZEBhREDUTnjj95UcfA XXQYgrE84w3wUKAGY6OPZbE+GXlU= X-Google-Smtp-Source: AGHT+IHO77pHEIuqXZIOPEe6uiRNUfiLP6s0v0MrYYBfr60+4iNIdFbVvBjzxWP7Gy5U4L2K2VJyENwd40xp2QR/MRc= X-Received: by 2002:a05:6808:398c:b0:3e5:f9e9:43c4 with SMTP id 5614622812f47-3e7e1079371mr518945b6e.18.1731965285752; Mon, 18 Nov 2024 13:28:05 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: "David G. Johnston" Date: Mon, 18 Nov 2024 14:27:29 -0700 Message-ID: Subject: Re: Default session role broken in PostgreSQL 14.14? To: Maxime Legault-Venne Cc: "pgsql-general@lists.postgresql.org" Content-Type: multipart/alternative; boundary="0000000000009ee671062736979a" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000009ee671062736979a Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Nov 18, 2024 at 2:24=E2=80=AFPM Maxime Legault-Venne < m.legault-venne@metrio.net> wrote: > > I noticed a change of behaviour since PostgreSQL 14.14 that is breaking > the permissions in my application: it looks like the =E2=80=9CALTER ROLE = IN > DATABASE SET ROLE =E2=80=9D is no longer applied when = is > connecting to the database. > Reported as a bug previously here and fixed in this week's out-of-band update. https://www.postgresql.org/message-id/CADOZwSb0UsEr4_UTFXC5k7=3DfyyK8uKXeku= cd+-uuGjJsGBfxgw@mail.gmail.com David J. --0000000000009ee671062736979a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Mon, Nov 18, 2024 at 2:24=E2=80=AFPM Maxime Legault-Ven= ne <m.legault-venne@metrio= .net> wrote:


I noticed a change of behaviour since PostgreSQL 14.= 14 that is breaking the permissions in my application: it looks like the = =E2=80=9CALTER ROLE <role> IN DATABASE <db> SET ROLE <sessio= n-role>=E2=80=9D is no longer applied when <role> is connecting to the database.


Repo= rted as a bug previously here and fixed in this week's out-of-band upda= te.

https:= //www.postgresql.org/message-id/CADOZwSb0UsEr4_UTFXC5k7=3DfyyK8uKXekucd+-uu= GjJsGBfxgw@mail.gmail.com

David J.

--0000000000009ee671062736979a--