From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Nathan Bossart <nathandbossart(at)gmail(dot)com> |
Subject: | Re: --sync-method isn't documented to take an argument |
Date: | 2023-10-04 14:51:59 |
Message-ID: | 2586962.1696431119@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Daniel Gustafsson <daniel(at)yesql(dot)se> writes:
> On 4 Oct 2023, at 16:39, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> I concluded a long time ago that it does nothing.
> It does nothing in our current doc rendering, but if someone would like to
> render docs with another style where it does make a difference it seems
> unhelpful to not be consistent.
To do that, we'd need some sort of agreement on what the possible
"class" values are and when to use each one. I've never seen any
documentation about that.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Nathan Bossart | 2023-10-04 14:52:11 | Re: stopgap fix for signal handling during restore_command |
Previous Message | Daniel Gustafsson | 2023-10-04 14:49:30 | Re: --sync-method isn't documented to take an argument |