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 1tDmwV-003By3-JP for pgsql-bugs@arkaria.postgresql.org; Wed, 20 Nov 2024 15:48:35 +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 1tDmwU-006riJ-8h for pgsql-bugs@arkaria.postgresql.org; Wed, 20 Nov 2024 15:48:34 +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 1tDmwT-006riB-Tt for pgsql-bugs@lists.postgresql.org; Wed, 20 Nov 2024 15:48:34 +0000 Received: from mail-oi1-x233.google.com ([2607:f8b0:4864:20::233]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tDmwR-002whA-6J for pgsql-bugs@lists.postgresql.org; Wed, 20 Nov 2024 15:48:33 +0000 Received: by mail-oi1-x233.google.com with SMTP id 5614622812f47-3e60e57a322so1223270b6e.3 for ; Wed, 20 Nov 2024 07:48:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1732117709; x=1732722509; darn=lists.postgresql.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=gnOO7R0w6a3Nz9VtpTJBBfdTdp770m5/Vhk+8/kQCRg=; b=Tj58xxLsxqYenCx4p1+9Hio+lPhjIMPuT/JThMN5vQqH8T4aP9ET3XT4YAZgRgs42X E96XU+AW+lZmSQAlLjMgW0LVB/MXlz18C+ce8ewz3iwnPf9sQh8AS+1tLpPrRDreJvjr EH8MzJJrbVUyPf7/FwxZ+b/lUfPs5WQUYQbxDxxJ3Riv+1lXTGBuzww1bjcu9NxMlQVl 94wAx336O2cj4+0B9jrQIrtCE8kApE+EZK61Va3JlkTcIZyP4MfKV0to8wNFf5r/tg/H NjW0W27c6Sf9NDbWt1jEGDcxpS4vY7C82qnDO0tw6OREDJPrdnb/pd1Xb5aQMmgOPhpa PRcg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1732117709; x=1732722509; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=gnOO7R0w6a3Nz9VtpTJBBfdTdp770m5/Vhk+8/kQCRg=; b=W6arBhDY97nINq0Da/7L42K8lgR6MISzEs45GxTcBoyFnPEKLG+h1UIb4VgIXc8Kcy dvcf8iRpdhAwKc1Y8JSNlu1huBY1pbarTxGeQVncLj5gy1Gqh4iuM6VN0IkrJLEhb0x0 cdUlB1kt4iHqCYxfe93wmBvxsVrTuLfyNBxYyGu7BCUC+UO9AkWYX9FnKpZ4dxmHrUk4 jZlt7Yr4gFArNa1XK9TYFCRaIZ4hNwtzoP7lCLtadlfIdewHubFJR7CRI1JaJdbnOX5I O4Gs3ykIa93uVUmjn77QaXK9001NelghNMm2zEECXqGSGK1AGvUMAvCVGEbAazsDtFzE yh2A== X-Forwarded-Encrypted: i=1; AJvYcCVUsat08LgIPG+qT2mzBMZGqsbB3009C1pScDRDvObZWXHdgHM0luyIIs3jQbo7G81ZkwVWHvt2Xg15@lists.postgresql.org X-Gm-Message-State: AOJu0YwhKFhaoSdZPPQFdTIztiCPUkBJfZ71FUBjf6TXVjPmTIMK+os/ C4UoDoYGZD16VJJNBEuGO/0wtwAqEzHxGJl/wVHhzOH2OwutzOyj X-Google-Smtp-Source: AGHT+IHKS8p2AbdVJH7RnIVkAi9yEHVSe+/1f0uOP9sK8/1884xDnb8mdL8c1YuLqcwMcF4NyS2g0w== X-Received: by 2002:a05:6808:f89:b0:3e5:dbb6:4b6b with SMTP id 5614622812f47-3e7eb7c9635mr3497542b6e.36.1732117709366; Wed, 20 Nov 2024 07:48:29 -0800 (PST) Received: from nathan (162-195-168-172.lightspeed.stlsmo.sbcglobal.net. [162.195.168.172]) by smtp.gmail.com with ESMTPSA id d75a77b69052e-4646a544c30sm11356611cf.57.2024.11.20.07.48.28 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 20 Nov 2024 07:48:29 -0800 (PST) Date: Wed, 20 Nov 2024 09:48:27 -0600 From: Nathan Bossart To: kolpasch@gmail.com, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #18717: ALTER ROLE SET ROLE functionality is broken Message-ID: References: <18717-6cddff21930a88e6@postgresql.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <18717-6cddff21930a88e6@postgresql.org> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Wed, Nov 20, 2024 at 12:33:41PM +0000, PG Bug reporting form wrote: > We grant the owner role to the login roles, and assign it by ALTER ROLE > SET ROLE = . As a result, when logging into the > database with a login role, it is automatically assigned the owner role. > > Starting with version 14.14, this behavior is broken, and the issue persists > in version 17.1. When connecting to the database with a login role, the > session is assigned an empty (none) value for the role, leaving users > without the necessary permissions. This should be fixed in the next set of minor versions scheduled for release tomorrow [0]. [0] https://postgr.es/c/7b88529 -- nathan