| From: | Marcos Pegoraro <marcos(at)f10(dot)com(dot)br> |
|---|---|
| To: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
| Cc: | Peter Smith <smithpb2250(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Better visualization of default values |
| Date: | 2025-02-06 19:08:24 |
| Message-ID: | CAB-JLwa1BwESd_OJZftOeaw4dSCg29rd1nhc3gLwYZ1N8yxwrw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Em qui., 6 de fev. de 2025 às 12:32, Greg Sabino Mullane <htamfids(at)gmail(dot)com>
escreveu:
> That seems a somewhat arbitrary goal for us to optimize for.
>
well, my goal was to standardize these values. As examples of
non standardization you have ...
"The default is typically 100 connections".
Tipically ? Is it 100 or not the default for it ?
"The default value is three connections" or "The default is one thousand
files"
Why three and not 3 or why thousand and not 1000 ?
Sometimes "an empty string", sometimes "empty", sometimes ''.
Sometimes "If this parameter is off (the default)", "Default is off",
"Default value is off"
So, if we move all them to the definition of that GUC they would be written
the same way, just that.
regards
Marcos
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Borisov | 2025-02-06 20:16:01 | Re: Optimization for lower(), upper(), casefold() functions. |
| Previous Message | Jeff Davis | 2025-02-06 19:08:03 | Re: Optimization for lower(), upper(), casefold() functions. |