From: Tom Lane <tgl@sss.pgh.pa.us>
To: jobinau@gmail.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19540: Inconsistent integer-to-octal formatting for
 permission GUCs in pg_settings (boot_val vs setting)
In-reply-to: <19540-e641040b089ab768@postgresql.org>
References: <19540-e641040b089ab768@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Tue, 30 Jun 2026 06:45:35 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2665562.1782835088.1@sss.pgh.pa.us>
Date: Tue, 30 Jun 2026 11:58:08 -0400
Message-ID: <2665563.1782835088@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2665563.1782835088%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> Steps to reproduce:
> postgres=# SELECT name, setting, boot_val
> FROM pg_settings
> WHERE name IN ('data_directory_mode', 'log_file_mode',
> 'unix_socket_permissions');

> Actual Result :
>           name           | setting | boot_val
> -------------------------+---------+----------
>  data_directory_mode     | 0700    | 448
>  log_file_mode           | 0600    | 384
>  unix_socket_permissions | 0777    | 511
> (3 rows)

Yeah, the min and max columns are confusing too.  That's because
we entrust the formatting to the "show_hook" for those variables,
and those hooks are defined to show the current value only.

Looking through the existing show_hooks, all the other ones seem to
be used to account for situations where the effective value depends on
more than just the GUC variable itself.  Maybe we should say that
a show_hook should be used only for that purpose and not for specially
formatting the value?  We could deal with these cases by inventing a
new GUC flag, say GUC_SHOW_IN_OCTAL, that could be applied to all the
relevant values.

			regards, tom lane