testgres 1.11.1__tar.gz → 1.12.0__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- testgres-1.12.0/PKG-INFO +232 -0
- testgres-1.12.0/README.md +204 -0
- {testgres-1.11.1 → testgres-1.12.0}/setup.py +5 -3
- {testgres-1.11.1/testgres → testgres-1.12.0/src}/__init__.py +3 -3
- {testgres-1.11.1/testgres → testgres-1.12.0/src}/backup.py +1 -1
- {testgres-1.11.1/testgres → testgres-1.12.0/src}/cache.py +2 -2
- {testgres-1.11.1/testgres → testgres-1.12.0/src}/config.py +2 -2
- testgres-1.12.0/src/exceptions.py +71 -0
- {testgres-1.11.1/testgres → testgres-1.12.0/src}/impl/port_manager__generic.py +1 -1
- {testgres-1.11.1/testgres → testgres-1.12.0/src}/node.py +3 -3
- {testgres-1.11.1/testgres → testgres-1.12.0/src}/utils.py +4 -4
- testgres-1.12.0/testgres.egg-info/PKG-INFO +232 -0
- testgres-1.12.0/testgres.egg-info/SOURCES.txt +43 -0
- {testgres-1.11.1 → testgres-1.12.0}/testgres.egg-info/requires.txt +1 -0
- {testgres-1.11.1 → testgres-1.12.0}/tests/helpers/global_data.py +3 -3
- {testgres-1.11.1 → testgres-1.12.0}/tests/test_config.py +5 -5
- {testgres-1.11.1 → testgres-1.12.0}/tests/test_os_ops_common.py +2 -2
- {testgres-1.11.1 → testgres-1.12.0}/tests/test_os_ops_remote.py +1 -1
- {testgres-1.11.1 → testgres-1.12.0}/tests/test_testgres_common.py +23 -23
- {testgres-1.11.1 → testgres-1.12.0}/tests/test_testgres_local.py +12 -12
- {testgres-1.11.1 → testgres-1.12.0}/tests/test_testgres_remote.py +7 -7
- {testgres-1.11.1 → testgres-1.12.0}/tests/test_utils.py +3 -3
- testgres-1.11.1/PKG-INFO +0 -236
- testgres-1.11.1/README.md +0 -209
- testgres-1.11.1/testgres/exceptions.py +0 -113
- testgres-1.11.1/testgres/operations/helpers.py +0 -55
- testgres-1.11.1/testgres/operations/local_ops.py +0 -601
- testgres-1.11.1/testgres/operations/os_ops.py +0 -145
- testgres-1.11.1/testgres/operations/raise_error.py +0 -57
- testgres-1.11.1/testgres/operations/remote_ops.py +0 -874
- testgres-1.11.1/testgres/plugins/__init__.py +0 -8
- testgres-1.11.1/testgres/plugins/pg_probackup2/pg_probackup2/__init__.py +0 -0
- testgres-1.11.1/testgres/plugins/pg_probackup2/pg_probackup2/app.py +0 -906
- testgres-1.11.1/testgres/plugins/pg_probackup2/pg_probackup2/gdb.py +0 -341
- testgres-1.11.1/testgres/plugins/pg_probackup2/pg_probackup2/init_helpers.py +0 -228
- testgres-1.11.1/testgres/plugins/pg_probackup2/pg_probackup2/storage/__init__.py +0 -0
- testgres-1.11.1/testgres/plugins/pg_probackup2/pg_probackup2/storage/fs_backup.py +0 -104
- testgres-1.11.1/testgres/plugins/pg_probackup2/pg_probackup2/tests/__init__.py +0 -0
- testgres-1.11.1/testgres/plugins/pg_probackup2/pg_probackup2/tests/test_basic.py +0 -104
- testgres-1.11.1/testgres/plugins/pg_probackup2/setup.py +0 -18
- testgres-1.11.1/testgres.egg-info/PKG-INFO +0 -236
- testgres-1.11.1/testgres.egg-info/SOURCES.txt +0 -60
- testgres-1.11.1/tests/__init__.py +0 -0
- testgres-1.11.1/tests/helpers/__init__.py +0 -0
- {testgres-1.11.1 → testgres-1.12.0}/LICENSE +0 -0
- {testgres-1.11.1 → testgres-1.12.0}/MANIFEST.in +0 -0
- {testgres-1.11.1 → testgres-1.12.0}/setup.cfg +0 -0
- {testgres-1.11.1/testgres → testgres-1.12.0/src}/api.py +0 -0
- {testgres-1.11.1/testgres → testgres-1.12.0/src}/connection.py +0 -0
- {testgres-1.11.1/testgres → testgres-1.12.0/src}/consts.py +0 -0
- {testgres-1.11.1/testgres → testgres-1.12.0/src}/decorators.py +0 -0
- {testgres-1.11.1/testgres → testgres-1.12.0/src}/defaults.py +0 -0
- {testgres-1.11.1/testgres → testgres-1.12.0/src}/enums.py +0 -0
- {testgres-1.11.1/testgres → testgres-1.12.0/src}/impl/port_manager__this_host.py +0 -0
- {testgres-1.11.1/testgres → testgres-1.12.0/src}/logger.py +0 -0
- {testgres-1.11.1/testgres → testgres-1.12.0/src}/node_app.py +0 -0
- {testgres-1.11.1/testgres → testgres-1.12.0/src}/port_manager.py +0 -0
- {testgres-1.11.1/testgres → testgres-1.12.0/src}/pubsub.py +0 -0
- {testgres-1.11.1/testgres → testgres-1.12.0/src}/standby.py +0 -0
- {testgres-1.11.1 → testgres-1.12.0}/testgres.egg-info/dependency_links.txt +0 -0
- {testgres-1.11.1 → testgres-1.12.0}/testgres.egg-info/top_level.txt +0 -0
- {testgres-1.11.1/testgres/operations → testgres-1.12.0/tests}/__init__.py +0 -0
- {testgres-1.11.1 → testgres-1.12.0}/tests/conftest.py +0 -0
- {testgres-1.11.1/testgres/plugins/pg_probackup2 → testgres-1.12.0/tests/helpers}/__init__.py +0 -0
- {testgres-1.11.1 → testgres-1.12.0}/tests/helpers/run_conditions.py +0 -0
- {testgres-1.11.1 → testgres-1.12.0}/tests/test_os_ops_local.py +0 -0
testgres-1.12.0/PKG-INFO
ADDED
|
@@ -0,0 +1,232 @@
|
|
|
1
|
+
Metadata-Version: 2.4
|
|
2
|
+
Name: testgres
|
|
3
|
+
Version: 1.12.0
|
|
4
|
+
Summary: Testing utility for PostgreSQL and its extensions
|
|
5
|
+
Home-page: https://github.com/postgrespro/testgres
|
|
6
|
+
Author: Postgres Professional
|
|
7
|
+
Author-email: testgres@postgrespro.ru
|
|
8
|
+
License: PostgreSQL
|
|
9
|
+
Keywords: test,testing,postgresql
|
|
10
|
+
Description-Content-Type: text/markdown
|
|
11
|
+
License-File: LICENSE
|
|
12
|
+
Requires-Dist: pg8000
|
|
13
|
+
Requires-Dist: port-for>=0.4
|
|
14
|
+
Requires-Dist: six>=1.9.0
|
|
15
|
+
Requires-Dist: psutil
|
|
16
|
+
Requires-Dist: packaging
|
|
17
|
+
Requires-Dist: testgres.os_ops<1.0.0,>=0.0.2
|
|
18
|
+
Dynamic: author
|
|
19
|
+
Dynamic: author-email
|
|
20
|
+
Dynamic: description
|
|
21
|
+
Dynamic: description-content-type
|
|
22
|
+
Dynamic: home-page
|
|
23
|
+
Dynamic: keywords
|
|
24
|
+
Dynamic: license
|
|
25
|
+
Dynamic: license-file
|
|
26
|
+
Dynamic: requires-dist
|
|
27
|
+
Dynamic: summary
|
|
28
|
+
|
|
29
|
+
[](https://travis-ci.com/github/postgrespro/testgres)
|
|
30
|
+
[](https://codecov.io/gh/postgrespro/testgres)
|
|
31
|
+
[](https://badge.fury.io/py/testgres)
|
|
32
|
+
|
|
33
|
+
[Documentation](https://postgrespro.github.io/testgres/)
|
|
34
|
+
|
|
35
|
+
# testgres
|
|
36
|
+
|
|
37
|
+
Utility for orchestrating temporary PostgreSQL clusters in Python tests. Supports Python 3.7.17 and newer.
|
|
38
|
+
|
|
39
|
+
## Installation
|
|
40
|
+
|
|
41
|
+
Install `testgres` from PyPI:
|
|
42
|
+
|
|
43
|
+
```sh
|
|
44
|
+
pip install testgres
|
|
45
|
+
```
|
|
46
|
+
|
|
47
|
+
Use a dedicated virtual environment for isolated test dependencies.
|
|
48
|
+
|
|
49
|
+
## Usage
|
|
50
|
+
|
|
51
|
+
### Environment
|
|
52
|
+
|
|
53
|
+
> Note: by default `testgres` invokes `initdb`, `pg_ctl`, and `psql` binaries found in `PATH`.
|
|
54
|
+
|
|
55
|
+
Specify a custom PostgreSQL installation in one of the following ways:
|
|
56
|
+
|
|
57
|
+
- Set the `PG_CONFIG` environment variable to point to the `pg_config` executable.
|
|
58
|
+
- Set the `PG_BIN` environment variable to point to the directory with PostgreSQL binaries.
|
|
59
|
+
|
|
60
|
+
Example:
|
|
61
|
+
|
|
62
|
+
```sh
|
|
63
|
+
export PG_BIN=$HOME/pg_16/bin
|
|
64
|
+
python my_tests.py
|
|
65
|
+
```
|
|
66
|
+
|
|
67
|
+
### Examples
|
|
68
|
+
|
|
69
|
+
Create a temporary node, run queries, and let `testgres` clean up automatically:
|
|
70
|
+
|
|
71
|
+
```python
|
|
72
|
+
# create a node with a random name, port, and data directory
|
|
73
|
+
with testgres.get_new_node() as node:
|
|
74
|
+
|
|
75
|
+
# run initdb
|
|
76
|
+
node.init()
|
|
77
|
+
|
|
78
|
+
# start PostgreSQL
|
|
79
|
+
node.start()
|
|
80
|
+
|
|
81
|
+
# execute a query in the default database
|
|
82
|
+
print(node.execute('select 1'))
|
|
83
|
+
|
|
84
|
+
# the node is stopped and its files are removed automatically
|
|
85
|
+
```
|
|
86
|
+
|
|
87
|
+
### Query helpers
|
|
88
|
+
|
|
89
|
+
`testgres` provides four helpers for executing queries against the node:
|
|
90
|
+
|
|
91
|
+
| Command | Description |
|
|
92
|
+
|---------|-------------|
|
|
93
|
+
| `node.psql(query, ...)` | Runs the query via `psql` and returns a tuple `(returncode, stdout, stderr)`. |
|
|
94
|
+
| `node.safe_psql(query, ...)` | Same as `psql()` but returns only `stdout` and raises if the command fails. |
|
|
95
|
+
| `node.execute(query, ...)` | Connects via `psycopg2` or `pg8000` (whichever is available) and returns a list of tuples. |
|
|
96
|
+
| `node.connect(dbname, ...)` | Returns a `NodeConnection` wrapper for executing multiple statements within a transaction. |
|
|
97
|
+
|
|
98
|
+
Example of transactional usage:
|
|
99
|
+
|
|
100
|
+
```python
|
|
101
|
+
with node.connect() as con:
|
|
102
|
+
con.begin('serializable')
|
|
103
|
+
print(con.execute('select %s', 1))
|
|
104
|
+
con.rollback()
|
|
105
|
+
```
|
|
106
|
+
|
|
107
|
+
### Logging
|
|
108
|
+
|
|
109
|
+
By default `cleanup()` removes all temporary files (data directories, logs, and so on) created by the API. Call `configure_testgres(node_cleanup_full=False)` before starting nodes if you want to keep logs for inspection.
|
|
110
|
+
|
|
111
|
+
> Note: context managers (the `with` statement) call `stop()` and `cleanup()` automatically.
|
|
112
|
+
|
|
113
|
+
`testgres` integrates with the standard [Python logging](https://docs.python.org/3/library/logging.html) module, so you can aggregate logs from multiple nodes:
|
|
114
|
+
|
|
115
|
+
```python
|
|
116
|
+
import logging
|
|
117
|
+
|
|
118
|
+
# write everything to /tmp/testgres.log
|
|
119
|
+
logging.basicConfig(filename='/tmp/testgres.log')
|
|
120
|
+
|
|
121
|
+
# enable logging and create two nodes
|
|
122
|
+
testgres.configure_testgres(use_python_logging=True)
|
|
123
|
+
node1 = testgres.get_new_node().init().start()
|
|
124
|
+
node2 = testgres.get_new_node().init().start()
|
|
125
|
+
|
|
126
|
+
node1.execute('select 1')
|
|
127
|
+
node2.execute('select 2')
|
|
128
|
+
|
|
129
|
+
# disable logging
|
|
130
|
+
testgres.configure_testgres(use_python_logging=False)
|
|
131
|
+
```
|
|
132
|
+
|
|
133
|
+
See `tests/test_simple.py` for a complete logging example.
|
|
134
|
+
|
|
135
|
+
### Backup and replication
|
|
136
|
+
|
|
137
|
+
Creating backups and spawning replicas is straightforward:
|
|
138
|
+
|
|
139
|
+
```python
|
|
140
|
+
with testgres.get_new_node('master') as master:
|
|
141
|
+
master.init().start()
|
|
142
|
+
|
|
143
|
+
with master.backup() as backup:
|
|
144
|
+
replica = backup.spawn_replica('replica').start()
|
|
145
|
+
replica.catchup()
|
|
146
|
+
|
|
147
|
+
print(replica.execute('postgres', 'select 1'))
|
|
148
|
+
```
|
|
149
|
+
|
|
150
|
+
### Benchmarks
|
|
151
|
+
|
|
152
|
+
Use `pgbench` through `testgres` to run quick benchmarks:
|
|
153
|
+
|
|
154
|
+
```python
|
|
155
|
+
with testgres.get_new_node('master') as master:
|
|
156
|
+
master.init().start()
|
|
157
|
+
|
|
158
|
+
result = master.pgbench_init(scale=2).pgbench_run(time=10)
|
|
159
|
+
print(result)
|
|
160
|
+
```
|
|
161
|
+
|
|
162
|
+
### Custom configuration
|
|
163
|
+
|
|
164
|
+
`testgres` ships with sensible defaults. Adjust them as needed with `default_conf()` and `append_conf()`:
|
|
165
|
+
|
|
166
|
+
```python
|
|
167
|
+
extra_conf = "shared_preload_libraries = 'postgres_fdw'"
|
|
168
|
+
|
|
169
|
+
with testgres.get_new_node().init() as master:
|
|
170
|
+
master.default_conf(fsync=True, allow_streaming=True)
|
|
171
|
+
master.append_conf('postgresql.conf', extra_conf)
|
|
172
|
+
```
|
|
173
|
+
|
|
174
|
+
`default_conf()` is called by `init()` and rewrites the configuration file. Apply `append_conf()` afterwards to keep custom lines.
|
|
175
|
+
|
|
176
|
+
### Remote mode
|
|
177
|
+
|
|
178
|
+
You can provision nodes on a remote host (Linux only) by wiring `RemoteOperations` into the configuration:
|
|
179
|
+
|
|
180
|
+
```python
|
|
181
|
+
from testgres import ConnectionParams, RemoteOperations, TestgresConfig, get_remote_node
|
|
182
|
+
|
|
183
|
+
conn_params = ConnectionParams(
|
|
184
|
+
host='example.com',
|
|
185
|
+
username='postgres',
|
|
186
|
+
ssh_key='/path/to/ssh/key'
|
|
187
|
+
)
|
|
188
|
+
os_ops = RemoteOperations(conn_params)
|
|
189
|
+
|
|
190
|
+
TestgresConfig.set_os_ops(os_ops=os_ops)
|
|
191
|
+
|
|
192
|
+
def test_basic_query():
|
|
193
|
+
with get_remote_node(conn_params=conn_params) as node:
|
|
194
|
+
node.init().start()
|
|
195
|
+
assert node.execute('SELECT 1') == [(1,)]
|
|
196
|
+
```
|
|
197
|
+
|
|
198
|
+
### Pytest integration
|
|
199
|
+
|
|
200
|
+
Use fixtures to create and clean up nodes automatically when testing with `pytest`:
|
|
201
|
+
|
|
202
|
+
```python
|
|
203
|
+
import pytest
|
|
204
|
+
import testgres
|
|
205
|
+
|
|
206
|
+
@pytest.fixture
|
|
207
|
+
def pg_node():
|
|
208
|
+
node = testgres.get_new_node().init().start()
|
|
209
|
+
try:
|
|
210
|
+
yield node
|
|
211
|
+
finally:
|
|
212
|
+
node.stop()
|
|
213
|
+
node.cleanup()
|
|
214
|
+
|
|
215
|
+
def test_simple(pg_node):
|
|
216
|
+
assert pg_node.execute('select 1')[0][0] == 1
|
|
217
|
+
```
|
|
218
|
+
|
|
219
|
+
This pattern keeps tests concise and ensures that every node is stopped and removed even if the test fails.
|
|
220
|
+
|
|
221
|
+
### Scaling tips
|
|
222
|
+
|
|
223
|
+
- Run tests in parallel with `pytest -n auto` (requires `pytest-xdist`). Ensure each node uses a distinct port by setting `PGPORT` in the fixture or by passing the `port` argument to `get_new_node()`.
|
|
224
|
+
- Always call `node.cleanup()` after each test, or rely on context managers/fixtures that do it for you, to avoid leftover data directories.
|
|
225
|
+
- Prefer `node.safe_psql()` for lightweight assertions that should fail fast; use `node.execute()` when you need structured Python results.
|
|
226
|
+
|
|
227
|
+
## Authors
|
|
228
|
+
|
|
229
|
+
[Ildar Musin](https://github.com/zilder)
|
|
230
|
+
[Dmitry Ivanov](https://github.com/funbringer)
|
|
231
|
+
[Ildus Kurbangaliev](https://github.com/ildus)
|
|
232
|
+
[Yury Zhuravlev](https://github.com/stalkerg)
|
|
@@ -0,0 +1,204 @@
|
|
|
1
|
+
[](https://travis-ci.com/github/postgrespro/testgres)
|
|
2
|
+
[](https://codecov.io/gh/postgrespro/testgres)
|
|
3
|
+
[](https://badge.fury.io/py/testgres)
|
|
4
|
+
|
|
5
|
+
[Documentation](https://postgrespro.github.io/testgres/)
|
|
6
|
+
|
|
7
|
+
# testgres
|
|
8
|
+
|
|
9
|
+
Utility for orchestrating temporary PostgreSQL clusters in Python tests. Supports Python 3.7.17 and newer.
|
|
10
|
+
|
|
11
|
+
## Installation
|
|
12
|
+
|
|
13
|
+
Install `testgres` from PyPI:
|
|
14
|
+
|
|
15
|
+
```sh
|
|
16
|
+
pip install testgres
|
|
17
|
+
```
|
|
18
|
+
|
|
19
|
+
Use a dedicated virtual environment for isolated test dependencies.
|
|
20
|
+
|
|
21
|
+
## Usage
|
|
22
|
+
|
|
23
|
+
### Environment
|
|
24
|
+
|
|
25
|
+
> Note: by default `testgres` invokes `initdb`, `pg_ctl`, and `psql` binaries found in `PATH`.
|
|
26
|
+
|
|
27
|
+
Specify a custom PostgreSQL installation in one of the following ways:
|
|
28
|
+
|
|
29
|
+
- Set the `PG_CONFIG` environment variable to point to the `pg_config` executable.
|
|
30
|
+
- Set the `PG_BIN` environment variable to point to the directory with PostgreSQL binaries.
|
|
31
|
+
|
|
32
|
+
Example:
|
|
33
|
+
|
|
34
|
+
```sh
|
|
35
|
+
export PG_BIN=$HOME/pg_16/bin
|
|
36
|
+
python my_tests.py
|
|
37
|
+
```
|
|
38
|
+
|
|
39
|
+
### Examples
|
|
40
|
+
|
|
41
|
+
Create a temporary node, run queries, and let `testgres` clean up automatically:
|
|
42
|
+
|
|
43
|
+
```python
|
|
44
|
+
# create a node with a random name, port, and data directory
|
|
45
|
+
with testgres.get_new_node() as node:
|
|
46
|
+
|
|
47
|
+
# run initdb
|
|
48
|
+
node.init()
|
|
49
|
+
|
|
50
|
+
# start PostgreSQL
|
|
51
|
+
node.start()
|
|
52
|
+
|
|
53
|
+
# execute a query in the default database
|
|
54
|
+
print(node.execute('select 1'))
|
|
55
|
+
|
|
56
|
+
# the node is stopped and its files are removed automatically
|
|
57
|
+
```
|
|
58
|
+
|
|
59
|
+
### Query helpers
|
|
60
|
+
|
|
61
|
+
`testgres` provides four helpers for executing queries against the node:
|
|
62
|
+
|
|
63
|
+
| Command | Description |
|
|
64
|
+
|---------|-------------|
|
|
65
|
+
| `node.psql(query, ...)` | Runs the query via `psql` and returns a tuple `(returncode, stdout, stderr)`. |
|
|
66
|
+
| `node.safe_psql(query, ...)` | Same as `psql()` but returns only `stdout` and raises if the command fails. |
|
|
67
|
+
| `node.execute(query, ...)` | Connects via `psycopg2` or `pg8000` (whichever is available) and returns a list of tuples. |
|
|
68
|
+
| `node.connect(dbname, ...)` | Returns a `NodeConnection` wrapper for executing multiple statements within a transaction. |
|
|
69
|
+
|
|
70
|
+
Example of transactional usage:
|
|
71
|
+
|
|
72
|
+
```python
|
|
73
|
+
with node.connect() as con:
|
|
74
|
+
con.begin('serializable')
|
|
75
|
+
print(con.execute('select %s', 1))
|
|
76
|
+
con.rollback()
|
|
77
|
+
```
|
|
78
|
+
|
|
79
|
+
### Logging
|
|
80
|
+
|
|
81
|
+
By default `cleanup()` removes all temporary files (data directories, logs, and so on) created by the API. Call `configure_testgres(node_cleanup_full=False)` before starting nodes if you want to keep logs for inspection.
|
|
82
|
+
|
|
83
|
+
> Note: context managers (the `with` statement) call `stop()` and `cleanup()` automatically.
|
|
84
|
+
|
|
85
|
+
`testgres` integrates with the standard [Python logging](https://docs.python.org/3/library/logging.html) module, so you can aggregate logs from multiple nodes:
|
|
86
|
+
|
|
87
|
+
```python
|
|
88
|
+
import logging
|
|
89
|
+
|
|
90
|
+
# write everything to /tmp/testgres.log
|
|
91
|
+
logging.basicConfig(filename='/tmp/testgres.log')
|
|
92
|
+
|
|
93
|
+
# enable logging and create two nodes
|
|
94
|
+
testgres.configure_testgres(use_python_logging=True)
|
|
95
|
+
node1 = testgres.get_new_node().init().start()
|
|
96
|
+
node2 = testgres.get_new_node().init().start()
|
|
97
|
+
|
|
98
|
+
node1.execute('select 1')
|
|
99
|
+
node2.execute('select 2')
|
|
100
|
+
|
|
101
|
+
# disable logging
|
|
102
|
+
testgres.configure_testgres(use_python_logging=False)
|
|
103
|
+
```
|
|
104
|
+
|
|
105
|
+
See `tests/test_simple.py` for a complete logging example.
|
|
106
|
+
|
|
107
|
+
### Backup and replication
|
|
108
|
+
|
|
109
|
+
Creating backups and spawning replicas is straightforward:
|
|
110
|
+
|
|
111
|
+
```python
|
|
112
|
+
with testgres.get_new_node('master') as master:
|
|
113
|
+
master.init().start()
|
|
114
|
+
|
|
115
|
+
with master.backup() as backup:
|
|
116
|
+
replica = backup.spawn_replica('replica').start()
|
|
117
|
+
replica.catchup()
|
|
118
|
+
|
|
119
|
+
print(replica.execute('postgres', 'select 1'))
|
|
120
|
+
```
|
|
121
|
+
|
|
122
|
+
### Benchmarks
|
|
123
|
+
|
|
124
|
+
Use `pgbench` through `testgres` to run quick benchmarks:
|
|
125
|
+
|
|
126
|
+
```python
|
|
127
|
+
with testgres.get_new_node('master') as master:
|
|
128
|
+
master.init().start()
|
|
129
|
+
|
|
130
|
+
result = master.pgbench_init(scale=2).pgbench_run(time=10)
|
|
131
|
+
print(result)
|
|
132
|
+
```
|
|
133
|
+
|
|
134
|
+
### Custom configuration
|
|
135
|
+
|
|
136
|
+
`testgres` ships with sensible defaults. Adjust them as needed with `default_conf()` and `append_conf()`:
|
|
137
|
+
|
|
138
|
+
```python
|
|
139
|
+
extra_conf = "shared_preload_libraries = 'postgres_fdw'"
|
|
140
|
+
|
|
141
|
+
with testgres.get_new_node().init() as master:
|
|
142
|
+
master.default_conf(fsync=True, allow_streaming=True)
|
|
143
|
+
master.append_conf('postgresql.conf', extra_conf)
|
|
144
|
+
```
|
|
145
|
+
|
|
146
|
+
`default_conf()` is called by `init()` and rewrites the configuration file. Apply `append_conf()` afterwards to keep custom lines.
|
|
147
|
+
|
|
148
|
+
### Remote mode
|
|
149
|
+
|
|
150
|
+
You can provision nodes on a remote host (Linux only) by wiring `RemoteOperations` into the configuration:
|
|
151
|
+
|
|
152
|
+
```python
|
|
153
|
+
from testgres import ConnectionParams, RemoteOperations, TestgresConfig, get_remote_node
|
|
154
|
+
|
|
155
|
+
conn_params = ConnectionParams(
|
|
156
|
+
host='example.com',
|
|
157
|
+
username='postgres',
|
|
158
|
+
ssh_key='/path/to/ssh/key'
|
|
159
|
+
)
|
|
160
|
+
os_ops = RemoteOperations(conn_params)
|
|
161
|
+
|
|
162
|
+
TestgresConfig.set_os_ops(os_ops=os_ops)
|
|
163
|
+
|
|
164
|
+
def test_basic_query():
|
|
165
|
+
with get_remote_node(conn_params=conn_params) as node:
|
|
166
|
+
node.init().start()
|
|
167
|
+
assert node.execute('SELECT 1') == [(1,)]
|
|
168
|
+
```
|
|
169
|
+
|
|
170
|
+
### Pytest integration
|
|
171
|
+
|
|
172
|
+
Use fixtures to create and clean up nodes automatically when testing with `pytest`:
|
|
173
|
+
|
|
174
|
+
```python
|
|
175
|
+
import pytest
|
|
176
|
+
import testgres
|
|
177
|
+
|
|
178
|
+
@pytest.fixture
|
|
179
|
+
def pg_node():
|
|
180
|
+
node = testgres.get_new_node().init().start()
|
|
181
|
+
try:
|
|
182
|
+
yield node
|
|
183
|
+
finally:
|
|
184
|
+
node.stop()
|
|
185
|
+
node.cleanup()
|
|
186
|
+
|
|
187
|
+
def test_simple(pg_node):
|
|
188
|
+
assert pg_node.execute('select 1')[0][0] == 1
|
|
189
|
+
```
|
|
190
|
+
|
|
191
|
+
This pattern keeps tests concise and ensures that every node is stopped and removed even if the test fails.
|
|
192
|
+
|
|
193
|
+
### Scaling tips
|
|
194
|
+
|
|
195
|
+
- Run tests in parallel with `pytest -n auto` (requires `pytest-xdist`). Ensure each node uses a distinct port by setting `PGPORT` in the fixture or by passing the `port` argument to `get_new_node()`.
|
|
196
|
+
- Always call `node.cleanup()` after each test, or rely on context managers/fixtures that do it for you, to avoid leftover data directories.
|
|
197
|
+
- Prefer `node.safe_psql()` for lightweight assertions that should fail fast; use `node.execute()` when you need structured Python results.
|
|
198
|
+
|
|
199
|
+
## Authors
|
|
200
|
+
|
|
201
|
+
[Ildar Musin](https://github.com/zilder)
|
|
202
|
+
[Dmitry Ivanov](https://github.com/funbringer)
|
|
203
|
+
[Ildus Kurbangaliev](https://github.com/ildus)
|
|
204
|
+
[Yury Zhuravlev](https://github.com/stalkerg)
|
|
@@ -11,7 +11,8 @@ install_requires = [
|
|
|
11
11
|
"port-for>=0.4",
|
|
12
12
|
"six>=1.9.0",
|
|
13
13
|
"psutil",
|
|
14
|
-
"packaging"
|
|
14
|
+
"packaging",
|
|
15
|
+
"testgres.os_ops>=0.0.2,<1.0.0"
|
|
15
16
|
]
|
|
16
17
|
|
|
17
18
|
# Add compatibility enum class
|
|
@@ -27,9 +28,10 @@ with open('README.md', 'r') as f:
|
|
|
27
28
|
readme = f.read()
|
|
28
29
|
|
|
29
30
|
setup(
|
|
30
|
-
version='1.
|
|
31
|
+
version='1.12.0',
|
|
31
32
|
name='testgres',
|
|
32
|
-
packages=['testgres', 'testgres.
|
|
33
|
+
packages=['testgres', 'testgres.impl'],
|
|
34
|
+
package_dir={"testgres": "src"},
|
|
33
35
|
description='Testing utility for PostgreSQL and its extensions',
|
|
34
36
|
url='https://github.com/postgrespro/testgres',
|
|
35
37
|
long_description=readme,
|
|
@@ -51,9 +51,9 @@ from .standby import \
|
|
|
51
51
|
|
|
52
52
|
from .config import testgres_config
|
|
53
53
|
|
|
54
|
-
from .operations.os_ops import OsOperations, ConnectionParams
|
|
55
|
-
from .operations.local_ops import LocalOperations
|
|
56
|
-
from .operations.remote_ops import RemoteOperations
|
|
54
|
+
from testgres.operations.os_ops import OsOperations, ConnectionParams
|
|
55
|
+
from testgres.operations.local_ops import LocalOperations
|
|
56
|
+
from testgres.operations.remote_ops import RemoteOperations
|
|
57
57
|
|
|
58
58
|
__all__ = [
|
|
59
59
|
"get_new_node",
|
|
@@ -16,8 +16,8 @@ from .utils import \
|
|
|
16
16
|
get_bin_path2, \
|
|
17
17
|
execute_utility2
|
|
18
18
|
|
|
19
|
-
from .operations.local_ops import LocalOperations
|
|
20
|
-
from .operations.os_ops import OsOperations
|
|
19
|
+
from testgres.operations.local_ops import LocalOperations
|
|
20
|
+
from testgres.operations.os_ops import OsOperations
|
|
21
21
|
|
|
22
22
|
|
|
23
23
|
def cached_initdb(data_dir, logfile=None, params=None, os_ops: OsOperations = None, bin_path=None, cached=True):
|
|
@@ -9,8 +9,8 @@ import tempfile
|
|
|
9
9
|
from contextlib import contextmanager
|
|
10
10
|
|
|
11
11
|
from .consts import TMP_CACHE
|
|
12
|
-
from .operations.os_ops import OsOperations
|
|
13
|
-
from .operations.local_ops import LocalOperations
|
|
12
|
+
from testgres.operations.os_ops import OsOperations
|
|
13
|
+
from testgres.operations.local_ops import LocalOperations
|
|
14
14
|
|
|
15
15
|
log_level = os.getenv('LOGGING_LEVEL', 'WARNING').upper()
|
|
16
16
|
log_format = os.getenv('LOGGING_FORMAT', '%(asctime)s - %(levelname)s - %(message)s')
|
|
@@ -0,0 +1,71 @@
|
|
|
1
|
+
# coding: utf-8
|
|
2
|
+
|
|
3
|
+
import six
|
|
4
|
+
|
|
5
|
+
from testgres.operations.exceptions import TestgresException
|
|
6
|
+
from testgres.operations.exceptions import ExecUtilException
|
|
7
|
+
from testgres.operations.exceptions import InvalidOperationException
|
|
8
|
+
|
|
9
|
+
|
|
10
|
+
class PortForException(TestgresException):
|
|
11
|
+
pass
|
|
12
|
+
|
|
13
|
+
|
|
14
|
+
@six.python_2_unicode_compatible
|
|
15
|
+
class QueryException(TestgresException):
|
|
16
|
+
def __init__(self, message=None, query=None):
|
|
17
|
+
super(QueryException, self).__init__(message)
|
|
18
|
+
|
|
19
|
+
self.message = message
|
|
20
|
+
self.query = query
|
|
21
|
+
|
|
22
|
+
def __str__(self):
|
|
23
|
+
msg = []
|
|
24
|
+
|
|
25
|
+
if self.message:
|
|
26
|
+
msg.append(self.message)
|
|
27
|
+
|
|
28
|
+
if self.query:
|
|
29
|
+
msg.append(u'Query: {}'.format(self.query))
|
|
30
|
+
|
|
31
|
+
return six.text_type('\n').join(msg)
|
|
32
|
+
|
|
33
|
+
|
|
34
|
+
class TimeoutException(QueryException):
|
|
35
|
+
pass
|
|
36
|
+
|
|
37
|
+
|
|
38
|
+
class CatchUpException(QueryException):
|
|
39
|
+
pass
|
|
40
|
+
|
|
41
|
+
|
|
42
|
+
@six.python_2_unicode_compatible
|
|
43
|
+
class StartNodeException(TestgresException):
|
|
44
|
+
def __init__(self, message=None, files=None):
|
|
45
|
+
super(StartNodeException, self).__init__(message)
|
|
46
|
+
|
|
47
|
+
self.message = message
|
|
48
|
+
self.files = files
|
|
49
|
+
|
|
50
|
+
def __str__(self):
|
|
51
|
+
msg = []
|
|
52
|
+
|
|
53
|
+
if self.message:
|
|
54
|
+
msg.append(self.message)
|
|
55
|
+
|
|
56
|
+
for f, lines in self.files or []:
|
|
57
|
+
msg.append(u'{}\n----\n{}\n'.format(f, lines))
|
|
58
|
+
|
|
59
|
+
return six.text_type('\n').join(msg)
|
|
60
|
+
|
|
61
|
+
|
|
62
|
+
class InitNodeException(TestgresException):
|
|
63
|
+
pass
|
|
64
|
+
|
|
65
|
+
|
|
66
|
+
class BackupException(TestgresException):
|
|
67
|
+
pass
|
|
68
|
+
|
|
69
|
+
|
|
70
|
+
assert ExecUtilException.__name__ == "ExecUtilException"
|
|
71
|
+
assert InvalidOperationException.__name__ == "InvalidOperationException"
|
|
@@ -104,9 +104,9 @@ from .utils import \
|
|
|
104
104
|
|
|
105
105
|
from .backup import NodeBackup
|
|
106
106
|
|
|
107
|
-
from .operations.os_ops import ConnectionParams
|
|
108
|
-
from .operations.os_ops import OsOperations
|
|
109
|
-
from .operations.local_ops import LocalOperations
|
|
107
|
+
from testgres.operations.os_ops import ConnectionParams
|
|
108
|
+
from testgres.operations.os_ops import OsOperations
|
|
109
|
+
from testgres.operations.local_ops import LocalOperations
|
|
110
110
|
|
|
111
111
|
InternalError = pglib.InternalError
|
|
112
112
|
ProgrammingError = pglib.ProgrammingError
|
|
@@ -15,10 +15,10 @@ from six import iteritems
|
|
|
15
15
|
|
|
16
16
|
from .exceptions import ExecUtilException
|
|
17
17
|
from .config import testgres_config as tconf
|
|
18
|
-
from .operations.os_ops import OsOperations
|
|
19
|
-
from .operations.remote_ops import RemoteOperations
|
|
20
|
-
from .operations.local_ops import LocalOperations
|
|
21
|
-
from .operations.helpers import Helpers as OsHelpers
|
|
18
|
+
from testgres.operations.os_ops import OsOperations
|
|
19
|
+
from testgres.operations.remote_ops import RemoteOperations
|
|
20
|
+
from testgres.operations.local_ops import LocalOperations
|
|
21
|
+
from testgres.operations.helpers import Helpers as OsHelpers
|
|
22
22
|
|
|
23
23
|
from .impl.port_manager__generic import PortManager__Generic
|
|
24
24
|
|