| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | "smithpb2250(at)gmail(dot)com" <smithpb2250(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, Nisha Moond <nisha(dot)moond412(at)gmail(dot)com>, Gunnar Morling <gunnar(dot)morling(at)googlemail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Unexpected behavior when setting "idle_replication_slot_timeout" |
| Date: | 2025-07-05 14:38:47 |
| Message-ID: | CAKFQuwaRFKJeUHKt2FdsUfm+0ZDpK8_7aAjUt-e_0a+27ZC8Zw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Saturday, July 5, 2025, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> wrote:
>
>
> I am sure that there is some information in these sentences, but I cannot
> extract it, even after reading them twice.
>
>
Maybe: “During checkpoint if the interval since
pg_replication_slots.inactive_since and now is larger than this value
pg_replication_slots.conflicting is set to true and
pg_replication_slots.inactive_reason is set to ‘timeout’. See section
wherever for more information on handling conflicted slots.”
Heck, writing this, “idle” is probably better, a slot can recover from
being idle on its own but usually inactive would imply having to do
something to make it active again.
IMO our documentation for replication has serious flaws but this particular
area is clear enough. Like any good timeout the slot is killed if it goes
unused “idle” for some length of time. We can describe that in many ways
but the name, to me, is fully descriptive and consistent with other
timeouts like “idle_in_transaction_timeout”.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2025-07-05 14:44:05 | Re: Unexpected behavior when setting "idle_replication_slot_timeout" |
| Previous Message | Kirill Reshke | 2025-07-05 11:45:43 | functional index search path issue. |