Re: [HACKERS] Restricting maximum keep segments by repslots
От | Kyotaro Horiguchi |
---|---|
Тема | Re: [HACKERS] Restricting maximum keep segments by repslots |
Дата | |
Msg-id | 20200410.115920.1130303270055020682.horikyota.ntt@gmail.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] Restricting maximum keep segments by repslots (Kyotaro Horiguchi <horikyota.ntt@gmail.com>) |
Список | pgsql-hackers |
At Wed, 08 Apr 2020 14:19:56 +0900 (JST), Kyotaro Horiguchi <horikyota.ntt@gmail.com> wrote in me> Just avoiding starting replication when restart_lsn is invalid is me> sufficient (the attached, which is equivalent to a part of what the me> invalidated flag did). I thing that the error message needs a Hint but me> it looks on the subscriber side as: At Wed, 08 Apr 2020 17:02:22 +0900 (JST), Kyotaro Horiguchi <horikyota.ntt@gmail.com> wrote in me> > At Wed, 08 Apr 2020 14:19:56 +0900 (JST), Kyotaro Horiguchi <horikyota.ntt@gmail.com> wrote in me> > The latch triggered by checkpoint request by CHECKPOINT command has me> > been absorbed by ConditionVariableSleep() in me> > InvalidateObsoleteReplicationSlots. The attached allows checkpointer me> > use MyLatch for other than checkpoint request while a checkpoint is me> > running. me> me> Checkpoint requests happens during waiting for the CV causes spurious me> wake up but that doesn't harm. I added the two above to open items[1] so as not to be forgotten. [1] https://wiki.postgresql.org/wiki/PostgreSQL_13_Open_Items#Open_Issues regards. -- Kyotaro Horiguchi NTT Open Source Software Center
В списке pgsql-hackers по дате отправления: