pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Michael Paquier <michael@paquier.xyz>
To: Nathan Bossart <nathandbossart@gmail.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Should we remove db_user_namespace?
Date: Thu, 6 Jul 2023 08:21:18 +0900
Message-ID: <ZKX67iJ2MxQVCgap@paquier.xyz> (raw)
In-Reply-To: <20230705212927.GA3518200@nathanxps13>
References: <20230630200509.GA2830328@nathanxps13>
	<ZKJ2xwbI1onh5hHB@paquier.xyz>
	<20230705212927.GA3518200@nathanxps13>

On Wed, Jul 05, 2023 at 02:29:27PM -0700, Nathan Bossart wrote:
>  	},
> -	{
> -		{"db_user_namespace", PGC_SIGHUP, CONN_AUTH_AUTH,
> -			gettext_noop("Enables per-database user names."),
> -			NULL
> -		},
> -		&Db_user_namespace,
> -		false,
> -		NULL, NULL, NULL
> -	},
>  	{

Removing the GUC from this table is kind of annoying.  Cannot this be
handled like default_with_oids or ssl_renegotiation_limit to avoid any
kind of issues with the reload of dump files and the kind?
--
Michael

Attachments:

  signature.asc (application/pgp-signature, 832B) download

view thread (17+ messages)  latest in thread

Message-ID: <ZKX67iJ2MxQVCgap@paquier.xyz>
Permalink:  ../ZKX67iJ2MxQVCgap@paquier.xyz/
Also on:    postgresql.org/message-id/ZKX67iJ2MxQVCgap@paquier.xyz

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: michael@paquier.xyz, nathandbossart@gmail.com
  Subject: Re: Should we remove db_user_namespace?
  In-Reply-To: <ZKX67iJ2MxQVCgap@paquier.xyz>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox