Re: BUG #18663: synchronous_standby_names vs synchronous_commit vs pg_stat_replication - Mailing list pgsql-bugs

From Asphator
Subject Re: BUG #18663: synchronous_standby_names vs synchronous_commit vs pg_stat_replication
Date
Msg-id CAOyVG+vKTug0wC9HV1RBS+_tQXNZu-5LGRgpcqjS5Ra1fCuhvw@mail.gmail.com
Whole thread Raw
In response to Re: BUG #18663: synchronous_standby_names vs synchronous_commit vs pg_stat_replication  (Fujii Masao <masao.fujii@oss.nttdata.com>)
List pgsql-bugs
Hello

I've just made the test and now, indeed, i understand the choice and agree with it.
So basically:

Thx for the push.


Le jeu. 9 janv. 2025 à 13:11, Fujii Masao <masao.fujii@oss.nttdata.com> a écrit :


On 2025/01/09 9:35, Fujii Masao wrote:
>
>
> On 2024/10/21 18:43, Fujii Masao wrote:
>>
>>
>> On 2024/10/18 23:48, PG Bug reporting form wrote:
>>> The following bug has been logged on the website:
>>>
>>> Bug reference:      18663
>>> Logged by:          Asphator
>>> Email address:      asphator@gmail.com
>>> PostgreSQL version: 15.7
>>> Operating system:   RHEL7+
>>> Description:
>>>
>>> Hello
>>>
>>> I would like to raise 2 issues:
>>> - documentation issue
>>> - pg_stat_replication view issue in a very specific use case
>>>
>>> 1. Documentation
>>> Regarding parameter synchronous_standby_names, I did not manage to find
>>> anything in documentation preventing from setting value 0. The only thing
>>> I've found is a comment in a commit of 2016. Would be nice to mention in
>>> documentation that value must be a "positive" integer.
>>
>> Agreed. I've attached the patch.
>
> I made a slight wording adjustment.
> Unless there are objections, I'll commit the attached patch.

Pushed.

Regards,

--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION



--

____________________
S'instruire pour vaincre...

pgsql-bugs by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: BUG #18769: ldapscheme is not displayed in pg_hba_file_rules
Next
From: Tom Lane
Date:
Subject: Re: BUG #18770: The function 'packGraph ' causes a memory leak.