| From: | Joakim Lundgren <lundgren700(at)gmail(dot)com> |
|---|---|
| To: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Takes long time to "fail back" using pg_rewind |
| Date: | 2018-10-04 11:19:45 |
| Message-ID: | CABcZ8inJaWGHSC1xO3MV5v=OtmH2aemxjwZHujdODd-yun7_Lg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Hi!
I experience that it takes a long time (several GB of data is fetched) to
use pg_rewind to do a failback when the former master has failed over to
the former standby (which is now master) and is started again and very
little data (like one row updated) is updated. I have upgraded to the
latest version (10.5), but still think it takes equally long time. I found
this bugfix (
https://www.postgresql.org/message-id/flat/0A3221C70F24FB45833433255569204D1F8D6C7A(at)G01JPEXMBYT05)
from late February this year. So would like to check if somebody knows if
this fix is incorporated in standard postgreSQL, or if anybody else
experience the same issue.
Thanks for any answer!
/Regards Joakim Lundgren
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joakim Lundgren | 2018-10-04 11:52:50 | Re: Takes long time to "fail back" using pg_rewind |
| Previous Message | Anders Wegge Keller | 2018-10-04 10:13:22 | Detect when streaming replication stops streaming. |