Re: Remove getpgusername()

From: Ian Lawrence Barwick <barwick(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Thom Brown <thom(at)linux(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Remove getpgusername()
Date: 2026-07-17 06:49:55
Message-ID: CAB8KJ=jyHVpeXQ3zQxStrp+rMx9gyBMzYfzykeKQg7TMrq4mkw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2026年7月17日(金) 7:51 Michael Paquier <michael(at)paquier(dot)xyz>:
>
> On Thu, Jul 16, 2026 at 08:00:51AM +0900, Michael Paquier wrote:
> > That's what I call a historical artifact. Removing it looks to be
> > simply a cleanup of pg_proc.dat. Will do so if there are no
> > objections, freeing an OID is not a bad thing here.
>
> And done this part.
>
> > Documenting it would not hurt, yes. We use it a lot in the regression
> > tests, perhaps some extensions would gain some portability ideas if we
> > publish a few words about it.
>
> For this part, if somebody has a patch, feel free.

I was feeling free, but the more I looked at it, the more horribly
inconsistent and ugly
"getdatabaseencoding()" is as a public SQL function name, and we have
"pg_client_encoding()" already, so might as well rename it?

Patch in separate thread:
https://www.postgresql.org/message-id/CAB8KJ%3DiQQ3j1ZzJkgF_CGF5TvJsugp6JFOrS-LB7kT%3DXivV_Vg%40mail.gmail.com

Regards

Ian Barwick

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Smith 2026-07-17 06:56:49 Re: Support EXCEPT for TABLES IN SCHEMA publications
Previous Message Ian Lawrence Barwick 2026-07-17 06:44:50 [PATCH] Rename "getdatabaseencoding()" to "pg_database_encoding()", and document