agora inbox for pgsql-bugs@postgresql.org  

help / color / mirror / Atom feed

From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: jobinau@gmail.com
Subject: BUG #19540: Inconsistent integer-to-octal formatting for permission GUCs in pg_settings (boot_val vs setting)
Date: Tue, 30 Jun 2026 06:45:35 +0000
Message-ID: <19540-e641040b089ab768@postgresql.org> (raw)

The following bug has been logged on the website:

Bug reference:      19540
Logged by:          Jobin Augustine
Email address:      jobinau@gmail.com
PostgreSQL version: 18.4
Operating system:   All
Description:        

This is more of an undocumented behavior in all PostgreSQL versions.

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)

File/Directory permissions like 448,384 and 511 may not make a good sense
for a user. Either a decoded value or mentioning it in docs would be great.
Displaying the value consistent with "setting" column is most desirable from
a user perspective.

Thank you,
Jobin.

view thread (2+ messages)  latest in thread

Message-ID: <19540-e641040b089ab768@postgresql.org>
Permalink:  ../../19540-e641040b089ab768@postgresql.org/
Also on:    postgresql.org/message-id/19540-e641040b089ab768@postgresql.org

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-bugs@postgresql.org
  Cc: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, jobinau@gmail.com
  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>

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

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