Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qFLfy-0001Rp-IO for pgsql-hackers@arkaria.postgresql.org; Fri, 30 Jun 2023 21:29:10 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1qFLfx-0007ye-Ez for pgsql-hackers@arkaria.postgresql.org; Fri, 30 Jun 2023 21:29:09 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qFLfx-0007yU-5q for pgsql-hackers@lists.postgresql.org; Fri, 30 Jun 2023 21:29:09 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qFLfu-001Rn0-By for pgsql-hackers@postgresql.org; Fri, 30 Jun 2023 21:29:08 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2023062407; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description; bh=I8c3KP11Ycvn5Mczo5LBsZvzULL0XwI/jF5aG5EXQBk=; b=0XPY9 KKe5QiOf0o18/h48i/QnRFC9aBH6vV9A2TcPiSM3zEhq34bhGwVLdVmyUXyR4uYjDnLBCqH58LWav ftO6O6xoVBSww9NfLD1ymu1P33PIPcOZfGDUWos9W4mFXMv4leVrSQJplIMpjmMLYZT9kPhScyqXN B297F1ZwkV6UbjtXQ04KEeRXqJkqjhToDHIr9jIDiXfvLD5LiFa0WCpCp7NqqjZAGNKB8Eft8FIs1 OhpzYcXiPZ4TH2ex+Ye9+CjRUaAZ6ZqAsfpr+ijOaI8WPbxDmPWzoc2q0zaUvSGYF3QZFKN6jza// +JlGkZ5Ekm/sp/sm9Qx0sbvJdjNlw==; Received: from bruce by momjian.us with local (Exim 4.94.2) (envelope-from ) id 1qFLfs-0023F3-Dy; Fri, 30 Jun 2023 17:29:04 -0400 Date: Fri, 30 Jun 2023 17:29:04 -0400 From: Bruce Momjian To: Nathan Bossart Cc: pgsql-hackers@postgresql.org Subject: Re: Should we remove db_user_namespace? Message-ID: References: <20230630200509.GA2830328@nathanxps13> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230630200509.GA2830328@nathanxps13> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, Jun 30, 2023 at 01:05:09PM -0700, Nathan Bossart wrote: > I think this is the second decennial thread [0] for removing this GUC. > This topic came up at PGCon, so I thought I'd start the discussion on the > lists. > > I'm personally not aware of anyone using this parameter. A couple of my > colleagues claimed to have used it in the aughts, but they also noted that > users were confused by the current implementation, and they seemed > generally in favor of removing it. AFAICT the strongest reason for keeping > it is that there is presently no viable replacement. Does this opinion > still stand? If so, perhaps we can look into adding a viable replacement > for v17. I am the original author, and it was a hack designed to support per-database user names. I am fine with its removal. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Only you can decide what is important to you.