Re: pg_rewind in contrib
| От | Venkata Balaji N |
|---|---|
| Тема | Re: pg_rewind in contrib |
| Дата | |
| Msg-id | CAEyp7J-vDiF4Wc0e=G9oJC=+LuBwZNjjo-UV5hki5-iXg8SkBg@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: pg_rewind in contrib (Heikki Linnakangas <hlinnaka@iki.fi>) |
| Ответы |
Re: pg_rewind in contrib
|
| Список | pgsql-hackers |
I have committed this, with some more kibitzing. hope I have not missed any comments given so far. Many thanks for the review, and please continue reviewing and testing it :-).
I had a streaming replication setup with one master and one slave running successfully.
Test 1 :
- Killed postgres process on master and promoted slave. Both were in sync earlier.
- performed some operations (data changes) on newly promoted slave node and shutdown
- Executed pg_rewind on old master and got the below message
target server must be shut down cleanly
Failure, exiting
If the master is crashed or killed abruptly, it may not be possible to do a rewind. Is my understanding correct ?Test 2 :
- On a successfully running streaming replication with one master and one slave, i did a clean shutdown of master
- promoted slave
- performed some operations (data changes) on newly promoted slave and did a clean shutdown
- Executed pg_rewind on the old master to sync with the latest changes on new master. I got the below message
The servers diverged at WAL position 0/A2000098 on timeline 1.
No rewind required.
I am not getting this too.
Regards,
Venkata Balaji N
В списке pgsql-hackers по дате отправления: