From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Should we remove db_user_namespace? |
Date: | 2023-06-30 20:05:09 |
Message-ID: | 20230630200509.GA2830328@nathanxps13 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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.
The attached patch simply removes the GUC.
[0] https://postgr.es/m/CAA-aLv6wnwp6Qr5fZo%2B7K%3DVSr51qFMuLsCeYvTkSF3E5qEPvqA%40mail.gmail.com
--
Nathan Bossart
Amazon Web Services: https://aws.amazon.com
Attachment | Content-Type | Size |
---|---|---|
v1-0001-remove-db_user_namespace.patch | text/x-diff | 7.5 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | David Christensen | 2023-06-30 20:05:54 | Re: Initdb-time block size specification |
Previous Message | Andres Freund | 2023-06-30 19:39:42 | Re: Initdb-time block size specification |