From: | Tomonari Katsumata <t(dot)katsumata1122(at)gmail(dot)com> |
---|---|
To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
Cc: | pgsql-docs(at)postgresql(dot)org |
Subject: | Re: Behavior of recovery_target_inclusive. |
Date: | 2017-10-24 00:43:45 |
Message-ID: | CAC55fYdSS80-bTqc7Z=MGvH=44e9ORAeQyXO7rarGhhr0_mCVA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
Hi Michael
Thanks for your reply and quick reaction.
2017-10-23 23:05 GMT+09:00 Michael Paquier <michael(dot)paquier(at)gmail(dot)com>:
> On Mon, Oct 23, 2017 at 10:27 PM, <t(dot)katsumata1122(at)gmail(dot)com> wrote:
> > At "recovery_target_inclusive (boolean)", nothing is
> mentioned about
> > "recovery_target_lsn".
> > It should be fixed, since "recovery_target_lsn" is affected
> by the value of
> > "recovery_target_inclusive".
> >
> > Could you check this?
>
> Apologies. You are right, this is a documentation bug and should be
> fixed. Attached is a patch to address the problem. The trend on the
> documentation page for recovery parameters is to list the options
> alphabetically, so recovery_target_lsn comes first.
> --
> Michael
>
Your patch seems good, but I have a question.
Does it need to fix the next sentence?
Like this:
----
This setting controls whether transactions having exactly the target WAL
location (LSN), commit time or ID, respectively, will be included in the
recovery.
----
Best regards,
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2017-10-24 00:45:31 | Re: Behavior of recovery_target_inclusive. |
Previous Message | Michael Paquier | 2017-10-23 14:05:49 | Re: Behavior of recovery_target_inclusive. |