pg_easy_replicate 0.2.3 → 0.2.4
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/CHANGELOG.md +13 -1
- data/Gemfile.lock +16 -16
- data/README.md +8 -0
- data/lib/pg_easy_replicate/query.rb +1 -1
- data/lib/pg_easy_replicate/version.rb +1 -1
- metadata +4 -4
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA256:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: fa012c1a56df04d2aad4d61e901a7affb409c24480d8b93d1b2806a08963c93e
|
4
|
+
data.tar.gz: 04ac8a97564f1d179f46f83f16e1bac495b19c6c10fa3af6a8f94ec6252dec3b
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: f3accba4733b9eaeb5d1acde1f299a967f487f5b6dee20a9bab0ecc31f0a8f4622cbfef5d449fd05bcf1d0a4c9b396796ad3b2663bb078162bfd7f878fd1054a
|
7
|
+
data.tar.gz: 16961c9f095ca3491e1231fbd5b2b934362141bbddca12b13988b84656f5e89d5fc72a759085a9d5105722e413869eb12c0d12feaacd1c8938149012d2548363
|
data/CHANGELOG.md
CHANGED
@@ -1,4 +1,16 @@
|
|
1
|
-
## [0.2.
|
1
|
+
## [0.2.3] - 2024-01-21
|
2
|
+
|
3
|
+
- Fix tables check in config_check - #93
|
4
|
+
- add option to skip vacuum analyzing on switchover - #92
|
5
|
+
- Disable statement timeout and reset it before/after vacuum+analyze - #94
|
6
|
+
- Add spec for skip_vacuum_analyze - #95
|
7
|
+
|
8
|
+
Highlights
|
9
|
+
|
10
|
+
- You can now skip vacuum and analyze by passing `--skip-vacuum-analyze` to `switchover`. Thanks to @honzasterba
|
11
|
+
- Vacuum and Analyze won't run into timeouts. Thanks to the report from @TrueCarry
|
12
|
+
|
13
|
+
## [0.2.2] - 2024-01-21
|
2
14
|
|
3
15
|
- Extend config check to assert for REPLICA IDENTITY on tables and drop index bug - #88
|
4
16
|
|
data/Gemfile.lock
CHANGED
@@ -1,19 +1,19 @@
|
|
1
1
|
PATH
|
2
2
|
remote: .
|
3
3
|
specs:
|
4
|
-
pg_easy_replicate (0.2.
|
4
|
+
pg_easy_replicate (0.2.4)
|
5
5
|
ougai (~> 2.0.0)
|
6
6
|
pg (~> 1.5.3)
|
7
|
-
sequel (>= 5.69, < 5.
|
7
|
+
sequel (>= 5.69, < 5.78)
|
8
8
|
thor (>= 1.2.2, < 1.4.0)
|
9
9
|
|
10
10
|
GEM
|
11
11
|
remote: https://rubygems.org/
|
12
12
|
specs:
|
13
13
|
ast (2.4.2)
|
14
|
-
bigdecimal (3.1.
|
14
|
+
bigdecimal (3.1.6)
|
15
15
|
coderay (1.1.3)
|
16
|
-
diff-lcs (1.5.
|
16
|
+
diff-lcs (1.5.1)
|
17
17
|
haml (6.1.1)
|
18
18
|
temple (>= 0.8.2)
|
19
19
|
thor
|
@@ -39,19 +39,19 @@ GEM
|
|
39
39
|
rbs (3.1.0)
|
40
40
|
regexp_parser (2.9.0)
|
41
41
|
rexml (3.2.6)
|
42
|
-
rspec (3.
|
43
|
-
rspec-core (~> 3.
|
44
|
-
rspec-expectations (~> 3.
|
45
|
-
rspec-mocks (~> 3.
|
46
|
-
rspec-core (3.
|
47
|
-
rspec-support (~> 3.
|
48
|
-
rspec-expectations (3.
|
42
|
+
rspec (3.13.0)
|
43
|
+
rspec-core (~> 3.13.0)
|
44
|
+
rspec-expectations (~> 3.13.0)
|
45
|
+
rspec-mocks (~> 3.13.0)
|
46
|
+
rspec-core (3.13.0)
|
47
|
+
rspec-support (~> 3.13.0)
|
48
|
+
rspec-expectations (3.13.0)
|
49
49
|
diff-lcs (>= 1.2.0, < 2.0)
|
50
|
-
rspec-support (~> 3.
|
51
|
-
rspec-mocks (3.
|
50
|
+
rspec-support (~> 3.13.0)
|
51
|
+
rspec-mocks (3.13.0)
|
52
52
|
diff-lcs (>= 1.2.0, < 2.0)
|
53
|
-
rspec-support (~> 3.
|
54
|
-
rspec-support (3.
|
53
|
+
rspec-support (~> 3.13.0)
|
54
|
+
rspec-support (3.13.0)
|
55
55
|
rubocop (1.60.1)
|
56
56
|
json (~> 2.3)
|
57
57
|
language_server-protocol (>= 3.17.0)
|
@@ -81,7 +81,7 @@ GEM
|
|
81
81
|
rubocop-capybara (~> 2.17)
|
82
82
|
rubocop-factory_bot (~> 2.22)
|
83
83
|
ruby-progressbar (1.13.0)
|
84
|
-
sequel (5.
|
84
|
+
sequel (5.77.0)
|
85
85
|
bigdecimal
|
86
86
|
syntax_tree (6.2.0)
|
87
87
|
prettier_print (>= 1.2.0)
|
data/README.md
CHANGED
@@ -76,6 +76,14 @@ $ export SOURCE_DB_URL="postgres://USERNAME:PASSWORD@localhost:5432/DATABASE_NAM
|
|
76
76
|
$ export TARGET_DB_URL="postgres://USERNAME:PASSWORD@localhost:5433/DATABASE_NAME"
|
77
77
|
```
|
78
78
|
|
79
|
+
**Optional**
|
80
|
+
|
81
|
+
You can extend the default timeout by setting the following environment variable
|
82
|
+
|
83
|
+
```bash
|
84
|
+
$ export PG_EASY_REPLICATE_STATEMENT_TIMEOUT="10s" # default 5s
|
85
|
+
```
|
86
|
+
|
79
87
|
Any `pg_easy_replicate` command can be run the same way with the docker image as well. As long the container is running in an environment where it has access to both the databases. Example
|
80
88
|
|
81
89
|
```bash
|
metadata
CHANGED
@@ -1,14 +1,14 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: pg_easy_replicate
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.2.
|
4
|
+
version: 0.2.4
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Shayon Mukherjee
|
8
8
|
autorequire:
|
9
9
|
bindir: bin
|
10
10
|
cert_chain: []
|
11
|
-
date: 2024-
|
11
|
+
date: 2024-02-13 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
name: ougai
|
@@ -47,7 +47,7 @@ dependencies:
|
|
47
47
|
version: '5.69'
|
48
48
|
- - "<"
|
49
49
|
- !ruby/object:Gem::Version
|
50
|
-
version: '5.
|
50
|
+
version: '5.78'
|
51
51
|
type: :runtime
|
52
52
|
prerelease: false
|
53
53
|
version_requirements: !ruby/object:Gem::Requirement
|
@@ -57,7 +57,7 @@ dependencies:
|
|
57
57
|
version: '5.69'
|
58
58
|
- - "<"
|
59
59
|
- !ruby/object:Gem::Version
|
60
|
-
version: '5.
|
60
|
+
version: '5.78'
|
61
61
|
- !ruby/object:Gem::Dependency
|
62
62
|
name: thor
|
63
63
|
requirement: !ruby/object:Gem::Requirement
|