BUG #19540: Inconsistent integer-to-octal formatting for permission GUCs in pg_settings (boot_val vs setting)

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.