| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Cc: | Jobin Augustine <jobinau(at)gmail(dot)com> |
| Subject: | Improving display of octal GUCs |
| Date: | 2026-06-30 20:32:15 |
| Message-ID: | 3006313.1782851535@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
It's customary to write the values of unix_socket_permissions
and a few other GUCs in octal. However, we implemented that
via show_hooks, which don't affect any pg_settings columns
except the current value. So you get results like this:
regression=# SELECT name,setting,min_val,max_val,boot_val,reset_val
FROM pg_settings
WHERE name IN ('data_directory_mode', 'log_file_mode', 'unix_socket_permissions');
name | setting | min_val | max_val | boot_val | reset_val
-------------------------+---------+---------+---------+----------+-----------
data_directory_mode | 0700 | 0 | 511 | 448 | 448
log_file_mode | 0600 | 0 | 511 | 384 | 384
unix_socket_permissions | 0777 | 0 | 511 | 511 | 511
(3 rows)
That's always been a niggling annoyance, and we recently got a bug
report complaining about it [1]. So here's an attempt to improve
matters:
regression=# SELECT name,setting,min_val,max_val,boot_val,reset_val
FROM pg_settings
WHERE name IN ('data_directory_mode', 'log_file_mode', 'unix_socket_permissions');
name | setting | min_val | max_val | boot_val | reset_val
-------------------------+---------+---------+---------+----------+-----------
data_directory_mode | 0700 | 0000 | 0777 | 0700 | 0700
log_file_mode | 0600 | 0000 | 0777 | 0600 | 0600
unix_socket_permissions | 0777 | 0000 | 0777 | 0777 | 0777
(3 rows)
Details in the draft commit message.
regards, tom lane
[1] https://www.postgresql.org/message-id/flat/19540-e641040b089ab768%40postgresql.org
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-Improve-display-of-GUCs-that-are-customarily-writ.patch | text/x-diff | 14.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2026-06-30 20:32:19 | Re: Global temporary tables |
| Previous Message | Jelte Fennema-Nio | 2026-06-30 20:27:51 | Re: Correct documentation for protocol version |