Re: Should we remove db_user_namespace?

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Nathan Bossart <nathandbossart(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Should we remove db_user_namespace?
Date: 2023-06-30 21:29:04
Message-ID: ZJ9JILgzHoHDKX6d@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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 <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com

Only you can decide what is important to you.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Christensen 2023-06-30 21:29:40 Re: Initdb-time block size specification
Previous Message David Christensen 2023-06-30 21:28:59 Re: Initdb-time block size specification