Re: Improving display of octal GUCs

From: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Rui Zhao <zhaorui126(at)gmail(dot)com>, Tatsuya Kawata <kawatatatsuya0913(at)gmail(dot)com>, fabriziomello(at)gmail(dot)com, pgsql-hackers mailing list <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Jobin Augustine <jobinau(at)gmail(dot)com>
Subject: Re: Improving display of octal GUCs
Date: 2026-09-03 17:02:15
Message-ID: 8C54F179-BA3B-48D9-A00D-41EFA4207D7B@yandex-team.ru
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> In the initial draft, I felt that showing the interpreted value in
> octal would be enough of a clue, but perhaps that judgment is wrong.

I think showing 01200 together with the valid range (0000 .. 0777) is
already enough of a clue. I would not add a HINT.

Best regards, Andrey Borodin.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jacob Champion 2026-09-03 17:10:36 Do we want to avoid checksumming extra files in the datadir? [was: BUG #19647]
Previous Message Paul A Jungwirth 2026-09-03 17:01:09 Re: FOR PORTION OF: BEFORE INSERT triggers can silently drop leftover rows?