gopkg/pgx
2
0
Fork 0
Code Activity

Extract replication to pgxrepl package

Browse Source
This commit is contained in:
Jack Christensen
2019-05-25 10:19:57 -05:00
parent dd8c63c839
commit 159d82e772
4 changed files with 0 additions and 841 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
-21
View File
@@ -97,7 +97,6 @@ Then run the following SQL:
create user pgx_md5 password 'secret';
create user " tricky, ' } "" \ test user " password 'secret';
create database pgx_test;
create user pgx_replication with replication password 'secret';
Connect to database pgx_test and run:
@@ -141,26 +140,6 @@ Each different test connection type uses a different connection string in an env
export PGX_TEST_MD5_PASSWORD_CONN_STRING="host=127.0.0.1 user=pgx_md5 password=secret database=pgx_test"
export PGX_TEST_PLAIN_PASSWORD_CONN_STRING="host=127.0.0.1 user=pgx_pw password=secret database=pgx_test"
### Replication Test Environment
Add a replication user:
create user pgx_replication with replication password 'secret';
Add a replication line to your pg_hba.conf:
host replication pgx_replication 127.0.0.1/32 md5
Change the following settings in your postgresql.conf:
wal_level=logical
max_wal_senders=5
max_replication_slots=5
Set the replication environment variable.
export PGX_TEST_REPLICATION_CONN_STRING="host=127.0.0.1 user=pgx_replication password=secret database=pgx_test"
## Version Policy
pgx follows semantic versioning for the documented public API on stable releases. Branch `v3` is the latest stable release. `master` can contain new features or behavior that will change or be removed before being merged to the stable `v3` branch (in practice, this occurs very rarely). `v2` is the previous stable release.