| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Smith <smithpb2250(at)gmail(dot)com> |
| Cc: | David Rowley <dgrowleyml(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Docs: Always use true|false instead of sometimes on|off for the subscription options |
| Date: | 2024-05-16 16:40:50 |
| Message-ID: | 2111712.1715877650@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Smith <smithpb2250(at)gmail(dot)com> writes:
> Yeah, I had a vested interest in this one place because I've been
> reviewing the other thread [1] that was mentioned above. If that other
> thread chooses "true|false" then putting "true|false" adjacent to
> another "on|off" will look silly. But if that other thread adopts the
> existing 'failover=on|off' values then it will diverge even further
> from being consistent with the CREATE SUBSCRIPTION page.
It's intentional that we allow more than one spelling of boolean
values. I can see some value in being consistent within nearby
examples, but I don't agree at all that it should be uniform
across all our docs.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2024-05-16 16:57:40 | Re: Add new protocol message to change GUCs for usage with future protocol-only GUCs |
| Previous Message | Imseih (AWS), Sami | 2024-05-16 16:37:10 | Re: allow changing autovacuum_max_workers without restarting |