New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add catchup commands family #455
Conversation
7d0f769
to
bde5c0b
Compare
ab98487
to
0cef0c5
Compare
1413a31
to
573a12c
Compare
4d627bc
to
abb1a3c
Compare
832d5be
to
c8d903b
Compare
62899d2
to
5cae776
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually we have the main scenario to test this feature.
First
- Run HA cluster - 1 master and 1 replica.
- Run pgbench to fill cluster.
- After that block streaming WAL to replica by iptables(firstly check taht it's possible)
- Run pgbench again, after that master will have more data than replica
- Catchup-push from master PGDATA and from replica LSN.
- Replica catchup-fetch this incremental-backup
- Compare that master and replica has the same data.
P.S. It would be better to create several incremental backups which catchup-fetch will apply
docker/pg_tests/scripts/scripts/wait_while_replication_complete.sh
Outdated
Show resolved
Hide resolved
@@ -53,7 +53,8 @@ pgbench -i -s 100 -h 127.0.0.1 -p ${ALPHA_PORT} postgres | |||
|
|||
LSN=`psql -c "SELECT pg_current_wal_lsn() - '0/0'::pg_lsn;" | grep -E '[0-9]+' | head -1` | |||
|
|||
/tmp/scripts/wait_while_replication_complete.sh postgres pgbench_accounts ${BETA_PORT} | |||
# db table conn_port row_count |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool Idea!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Go imports 🎉, Go fmt 🎉, Go modules 🎉
* Rename test * Parametrize expected count of rows in wait_while_replication_complete.sh
#363 solution