db/pgbackrest
1
0
Fork 0
mirror of https://github.com/pgbackrest/pgbackrest.git synced 2024-12-14 10:13:05 +02:00
Code Issues Releases Activity
2789d3b620
pgbackrest/test/expect/mock-stanza-001.log

560 lines
35 KiB
Plaintext
Raw Normal View History

GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
run 001 - remote 0, storage gcs, enc 0, cmp zst
===============================================
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
Rename most instances of master to primary in tests. This aligns better with general PostgreSQL usage and our own documentation (updated in 4bcef702). Usage in the backup.manifest tests has not been updated since it might break the file format.
2020-06-16 20:06:38 +02:00
stanza-create db - fail on missing control file (db-primary host)
> [CONTAINER-EXEC] db-primary [BACKREST-BIN] --config=[TEST_PATH]/db-primary/pgbackrest.conf --stanza=db --no-online --log-level-file=[LOG-LEVEL-FILE] stanza-create
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
------------------------------------------------------------------------------------------------------------------------------------
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
P00 INFO: stanza-create command begin [BACKREST-VERSION]: --buffer-size=[BUFFER-SIZE] --config=[TEST_PATH]/db-primary/pgbackrest.conf --db-timeout=45 --exec-id=[EXEC-ID] --lock-path=[TEST_PATH]/db-primary/lock --log-level-console=detail --log-level-file=[LOG-LEVEL-FILE] --log-level-stderr=off --log-path=[TEST_PATH]/db-primary/log[] --no-log-timestamp --no-online --pg1-path=[TEST_PATH]/db-primary/db/base --protocol-timeout=60 --repo1-gcs-bucket=gcsbucket --repo1-gcs-endpoint=gcs:4443 --repo1-gcs-key=<redacted> --repo1-gcs-key-type=token --repo1-path=/ --no-repo1-storage-verify-tls --repo1-type=gcs --stanza=db
Rename most instances of master to primary in tests. This aligns better with general PostgreSQL usage and our own documentation (updated in 4bcef702). Usage in the backup.manifest tests has not been updated since it might break the file format.
2020-06-16 20:06:38 +02:00
P00 ERROR: [055]: unable to open missing file '[TEST_PATH]/db-primary/db/base/global/pg_control' for read
The stanza-create/update/delete commands are implemented entirely in C. Contributed by Cynthia Shang.
2019-08-21 22:26:28 +02:00
P00 INFO: stanza-create command end: aborted with exception [055]
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
Rename most instances of master to primary in tests. This aligns better with general PostgreSQL usage and our own documentation (updated in 4bcef702). Usage in the backup.manifest tests has not been updated since it might break the file format.
2020-06-16 20:06:38 +02:00
stanza-upgrade db - fail on stanza not initialized since archive.info is missing (db-primary host)
> [CONTAINER-EXEC] db-primary [BACKREST-BIN] --config=[TEST_PATH]/db-primary/pgbackrest.conf --stanza=db --no-online stanza-upgrade
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
------------------------------------------------------------------------------------------------------------------------------------
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
P00 INFO: stanza-upgrade command begin [BACKREST-VERSION]: --buffer-size=[BUFFER-SIZE] --config=[TEST_PATH]/db-primary/pgbackrest.conf --db-timeout=45 --exec-id=[EXEC-ID] --lock-path=[TEST_PATH]/db-primary/lock --log-level-console=detail --log-level-file=[LOG-LEVEL-FILE] --log-level-stderr=off --log-path=[TEST_PATH]/db-primary/log[] --no-log-timestamp --no-online --pg1-path=[TEST_PATH]/db-primary/db/base --protocol-timeout=60 --repo1-gcs-bucket=gcsbucket --repo1-gcs-endpoint=gcs:4443 --repo1-gcs-key=<redacted> --repo1-gcs-key-type=token --repo1-path=/ --no-repo1-storage-verify-tls --repo1-type=gcs --stanza=db
Partial multi-repository implementation. Multi-repository implementations for the archive-push, check, info, stanza-create, stanza-upgrade, and stanza-delete commands. Multi-repo configuration is disabled so there should be no behavioral changes between these commands and their current single-repo implementations. Multi-repo documentation and integration tests are still in the multi-repo development branch. All unit tests work as multi-repo since they are able to bypass the configuration restrictions.
2021-01-21 22:21:50 +02:00
P00 INFO: stanza-upgrade for stanza 'db' on repo1
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
P00 ERROR: [055]: unable to load info file '/archive/db/archive.info' or '/archive/db/archive.info.copy':
FileMissingError: unable to open missing file '/archive/db/archive.info' for read
FileMissingError: unable to open missing file '/archive/db/archive.info.copy' for read
The stanza-create/update/delete commands are implemented entirely in C. Contributed by Cynthia Shang.
2019-08-21 22:26:28 +02:00
HINT: archive.info cannot be opened but is required to push/get WAL segments.
HINT: is archive_command configured correctly in postgresql.conf?
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
HINT: has a stanza-create been performed?
HINT: use --no-archive-check to disable archive checks during backup if you have an alternate archiving scheme.
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
P00 DETAIL: statistics: STATISTICS
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
P00 INFO: stanza-upgrade command end: aborted with exception [055]
Rename most instances of master to primary in tests. This aligns better with general PostgreSQL usage and our own documentation (updated in 4bcef702). Usage in the backup.manifest tests has not been updated since it might break the file format.
2020-06-16 20:06:38 +02:00
stanza-create db - successfully create the stanza (db-primary host)
> [CONTAINER-EXEC] db-primary [BACKREST-BIN] --config=[TEST_PATH]/db-primary/pgbackrest.conf --stanza=db --no-online stanza-create
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
------------------------------------------------------------------------------------------------------------------------------------
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
P00 INFO: stanza-create command begin [BACKREST-VERSION]: --buffer-size=[BUFFER-SIZE] --config=[TEST_PATH]/db-primary/pgbackrest.conf --db-timeout=45 --exec-id=[EXEC-ID] --lock-path=[TEST_PATH]/db-primary/lock --log-level-console=detail --log-level-file=[LOG-LEVEL-FILE] --log-level-stderr=off --log-path=[TEST_PATH]/db-primary/log[] --no-log-timestamp --no-online --pg1-path=[TEST_PATH]/db-primary/db/base --protocol-timeout=60 --repo1-gcs-bucket=gcsbucket --repo1-gcs-endpoint=gcs:4443 --repo1-gcs-key=<redacted> --repo1-gcs-key-type=token --repo1-path=/ --no-repo1-storage-verify-tls --repo1-type=gcs --stanza=db
Partial multi-repository implementation. Multi-repository implementations for the archive-push, check, info, stanza-create, stanza-upgrade, and stanza-delete commands. Multi-repo configuration is disabled so there should be no behavioral changes between these commands and their current single-repo implementations. Multi-repo documentation and integration tests are still in the multi-repo development branch. All unit tests work as multi-repo since they are able to bypass the configuration restrictions.
2021-01-21 22:21:50 +02:00
P00 INFO: stanza-create for stanza 'db' on repo1
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
P00 DETAIL: statistics: STATISTICS
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
P00 INFO: stanza-create command end: completed successfully
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
+ supplemental file: /backup/db/backup.info
-------------------------------------------
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
[backrest]
backrest-format=5
backrest-version="[VERSION-1]"
[db]
db-catalog-version=201306121
db-control-version=937
db-id=1
Automate generation of WAL and pg_control test files. The existing static files would not work with 32-bit or big-endian systems so create functions to generate these files dynamically rather than creating a bunch of new static files.
2017-11-19 03:02:54 +02:00
db-system-id=1000000000000000093
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
db-version="9.3"
[db:history]
Automate generation of WAL and pg_control test files. The existing static files would not work with 32-bit or big-endian systems so create functions to generate these files dynamically rather than creating a bunch of new static files.
2017-11-19 03:02:54 +02:00
1={"db-catalog-version":201306121,"db-control-version":937,"db-system-id":1000000000000000093,"db-version":"9.3"}
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
Improve performance of info file load/save. Info files required three copies in memory to be loaded (the original string, an ini representation, and the final info object). Not only was this memory inefficient but the Ini object does sequential scans when searching for keys making large files very slow to load. This has not been an issue since archive.info and backup.info are very small, but it becomes a big deal when loading manifests with hundreds of thousands of files. Instead of holding copies of the data in memory, use a callback to deliver the ini data directly to the object when loading. Use a similar method for save to avoid having an intermediate copy. Save is a bit complex because sections/keys must be written in alpha order or older versions of pgBackRest will not calculate the correct checksum. Also move the load retry logic to helper functions rather than embedding it in the Info object. This allows for more flexibility in loading and ensures that stack traces will be available when developing unit tests. Reviewed by Cynthia Shang.
2019-09-06 19:48:28 +02:00
[backrest]
backrest-checksum="[CHECKSUM]"
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
+ supplemental file: /archive/db/archive.info
---------------------------------------------
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
[backrest]
backrest-format=5
backrest-version="[VERSION-1]"
[db]
db-id=1
Automate generation of WAL and pg_control test files. The existing static files would not work with 32-bit or big-endian systems so create functions to generate these files dynamically rather than creating a bunch of new static files.
2017-11-19 03:02:54 +02:00
db-system-id=1000000000000000093
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
db-version="9.3"
[db:history]
Automate generation of WAL and pg_control test files. The existing static files would not work with 32-bit or big-endian systems so create functions to generate these files dynamically rather than creating a bunch of new static files.
2017-11-19 03:02:54 +02:00
1={"db-id":1000000000000000093,"db-version":"9.3"}
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
Improve performance of info file load/save. Info files required three copies in memory to be loaded (the original string, an ini representation, and the final info object). Not only was this memory inefficient but the Ini object does sequential scans when searching for keys making large files very slow to load. This has not been an issue since archive.info and backup.info are very small, but it becomes a big deal when loading manifests with hundreds of thousands of files. Instead of holding copies of the data in memory, use a callback to deliver the ini data directly to the object when loading. Use a similar method for save to avoid having an intermediate copy. Save is a bit complex because sections/keys must be written in alpha order or older versions of pgBackRest will not calculate the correct checksum. Also move the load retry logic to helper functions rather than embedding it in the Info object. This allows for more flexibility in loading and ensures that stack traces will be available when developing unit tests. Reviewed by Cynthia Shang.
2019-09-06 19:48:28 +02:00
[backrest]
backrest-checksum="[CHECKSUM]"
Rename most instances of master to primary in tests. This aligns better with general PostgreSQL usage and our own documentation (updated in 4bcef702). Usage in the backup.manifest tests has not been updated since it might break the file format.
2020-06-16 20:06:38 +02:00
stanza-create db - do not fail on rerun of stanza-create - info files exist and DB section ok (db-primary host)
> [CONTAINER-EXEC] db-primary [BACKREST-BIN] --config=[TEST_PATH]/db-primary/pgbackrest.conf --stanza=db --no-online stanza-create
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
------------------------------------------------------------------------------------------------------------------------------------
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
P00 INFO: stanza-create command begin [BACKREST-VERSION]: --buffer-size=[BUFFER-SIZE] --config=[TEST_PATH]/db-primary/pgbackrest.conf --db-timeout=45 --exec-id=[EXEC-ID] --lock-path=[TEST_PATH]/db-primary/lock --log-level-console=detail --log-level-file=[LOG-LEVEL-FILE] --log-level-stderr=off --log-path=[TEST_PATH]/db-primary/log[] --no-log-timestamp --no-online --pg1-path=[TEST_PATH]/db-primary/db/base --protocol-timeout=60 --repo1-gcs-bucket=gcsbucket --repo1-gcs-endpoint=gcs:4443 --repo1-gcs-key=<redacted> --repo1-gcs-key-type=token --repo1-path=/ --no-repo1-storage-verify-tls --repo1-type=gcs --stanza=db
Partial multi-repository implementation. Multi-repository implementations for the archive-push, check, info, stanza-create, stanza-upgrade, and stanza-delete commands. Multi-repo configuration is disabled so there should be no behavioral changes between these commands and their current single-repo implementations. Multi-repo documentation and integration tests are still in the multi-repo development branch. All unit tests work as multi-repo since they are able to bypass the configuration restrictions.
2021-01-21 22:21:50 +02:00
P00 INFO: stanza-create for stanza 'db' on repo1
P00 INFO: stanza 'db' already exists on repo1 and is valid
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
P00 DETAIL: statistics: STATISTICS
Improve stanza-create command so that it does not error when the stanza already exists. Contributed by Cynthia Shang.
2018-02-01 21:12:03 +02:00
P00 INFO: stanza-create command end: completed successfully
Repository encryption support. Contributed by Cynthia Shang.
2017-11-06 19:51:12 +02:00
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
+ supplemental file: /backup/db/backup.info
-------------------------------------------
Repository encryption support. Contributed by Cynthia Shang.
2017-11-06 19:51:12 +02:00
[backrest]
backrest-format=5
backrest-version="[VERSION-1]"
[db]
db-catalog-version=201306121
db-control-version=937
db-id=1
Automate generation of WAL and pg_control test files. The existing static files would not work with 32-bit or big-endian systems so create functions to generate these files dynamically rather than creating a bunch of new static files.
2017-11-19 03:02:54 +02:00
db-system-id=1000000000000000093
Repository encryption support. Contributed by Cynthia Shang.
2017-11-06 19:51:12 +02:00
db-version="9.3"
[db:history]
Automate generation of WAL and pg_control test files. The existing static files would not work with 32-bit or big-endian systems so create functions to generate these files dynamically rather than creating a bunch of new static files.
2017-11-19 03:02:54 +02:00
1={"db-catalog-version":201306121,"db-control-version":937,"db-system-id":1000000000000000093,"db-version":"9.3"}
Repository encryption support. Contributed by Cynthia Shang.
2017-11-06 19:51:12 +02:00
Improve performance of info file load/save. Info files required three copies in memory to be loaded (the original string, an ini representation, and the final info object). Not only was this memory inefficient but the Ini object does sequential scans when searching for keys making large files very slow to load. This has not been an issue since archive.info and backup.info are very small, but it becomes a big deal when loading manifests with hundreds of thousands of files. Instead of holding copies of the data in memory, use a callback to deliver the ini data directly to the object when loading. Use a similar method for save to avoid having an intermediate copy. Save is a bit complex because sections/keys must be written in alpha order or older versions of pgBackRest will not calculate the correct checksum. Also move the load retry logic to helper functions rather than embedding it in the Info object. This allows for more flexibility in loading and ensures that stack traces will be available when developing unit tests. Reviewed by Cynthia Shang.
2019-09-06 19:48:28 +02:00
[backrest]
backrest-checksum="[CHECKSUM]"
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
+ supplemental file: /archive/db/archive.info
---------------------------------------------
Repository encryption support. Contributed by Cynthia Shang.
2017-11-06 19:51:12 +02:00
[backrest]
backrest-format=5
backrest-version="[VERSION-1]"
[db]
db-id=1
Automate generation of WAL and pg_control test files. The existing static files would not work with 32-bit or big-endian systems so create functions to generate these files dynamically rather than creating a bunch of new static files.
2017-11-19 03:02:54 +02:00
db-system-id=1000000000000000093
Repository encryption support. Contributed by Cynthia Shang.
2017-11-06 19:51:12 +02:00
db-version="9.3"
[db:history]
Automate generation of WAL and pg_control test files. The existing static files would not work with 32-bit or big-endian systems so create functions to generate these files dynamically rather than creating a bunch of new static files.
2017-11-19 03:02:54 +02:00
1={"db-id":1000000000000000093,"db-version":"9.3"}
Repository encryption support. Contributed by Cynthia Shang.
2017-11-06 19:51:12 +02:00
Improve performance of info file load/save. Info files required three copies in memory to be loaded (the original string, an ini representation, and the final info object). Not only was this memory inefficient but the Ini object does sequential scans when searching for keys making large files very slow to load. This has not been an issue since archive.info and backup.info are very small, but it becomes a big deal when loading manifests with hundreds of thousands of files. Instead of holding copies of the data in memory, use a callback to deliver the ini data directly to the object when loading. Use a similar method for save to avoid having an intermediate copy. Save is a bit complex because sections/keys must be written in alpha order or older versions of pgBackRest will not calculate the correct checksum. Also move the load retry logic to helper functions rather than embedding it in the Info object. This allows for more flexibility in loading and ensures that stack traces will be available when developing unit tests. Reviewed by Cynthia Shang.
2019-09-06 19:48:28 +02:00
[backrest]
backrest-checksum="[CHECKSUM]"
Rename most instances of master to primary in tests. This aligns better with general PostgreSQL usage and our own documentation (updated in 4bcef702). Usage in the backup.manifest tests has not been updated since it might break the file format.
2020-06-16 20:06:38 +02:00
stanza-create db - fail on database mismatch and warn force option deprecated (db-primary host)
> [CONTAINER-EXEC] db-primary [BACKREST-BIN] --config=[TEST_PATH]/db-primary/pgbackrest.conf --stanza=db --no-online --force stanza-create
Repository encryption support. Contributed by Cynthia Shang.
2017-11-06 19:51:12 +02:00
------------------------------------------------------------------------------------------------------------------------------------
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
P00 INFO: stanza-create command begin [BACKREST-VERSION]: --buffer-size=[BUFFER-SIZE] --config=[TEST_PATH]/db-primary/pgbackrest.conf --db-timeout=45 --exec-id=[EXEC-ID] --force --lock-path=[TEST_PATH]/db-primary/lock --log-level-console=detail --log-level-file=[LOG-LEVEL-FILE] --log-level-stderr=off --log-path=[TEST_PATH]/db-primary/log[] --no-log-timestamp --no-online --pg1-path=[TEST_PATH]/db-primary/db/base --protocol-timeout=60 --repo1-gcs-bucket=gcsbucket --repo1-gcs-endpoint=gcs:4443 --repo1-gcs-key=<redacted> --repo1-gcs-key-type=token --repo1-path=/ --no-repo1-storage-verify-tls --repo1-type=gcs --stanza=db
The stanza-create/update/delete commands are implemented entirely in C. Contributed by Cynthia Shang.
2019-08-21 22:26:28 +02:00
P00 WARN: option --force is no longer supported
Partial multi-repository implementation. Multi-repository implementations for the archive-push, check, info, stanza-create, stanza-upgrade, and stanza-delete commands. Multi-repo configuration is disabled so there should be no behavioral changes between these commands and their current single-repo implementations. Multi-repo documentation and integration tests are still in the multi-repo development branch. All unit tests work as multi-repo since they are able to bypass the configuration restrictions.
2021-01-21 22:21:50 +02:00
P00 INFO: stanza-create for stanza 'db' on repo1
The check command is implemented entirely in C. Note that building the manifest on each host has been temporarily removed. This feature will likely be brought back as a non-default option (after the manifest code has been fully migrated to C) since it can be fairly expensive.
2019-10-09 00:04:09 +02:00
P00 ERROR: [028]: backup and archive info files exist but do not match the database
The stanza-create/update/delete commands are implemented entirely in C. Contributed by Cynthia Shang.
2019-08-21 22:26:28 +02:00
HINT: is this the correct stanza?
HINT: did an error occur during stanza-upgrade?
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
P00 DETAIL: statistics: STATISTICS
Repository encryption support. Contributed by Cynthia Shang.
2017-11-06 19:51:12 +02:00
P00 INFO: stanza-create command end: aborted with exception [028]
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
+ supplemental file: /backup/db/backup.info
-------------------------------------------
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
[backrest]
backrest-format=5
backrest-version="[VERSION-1]"
[db]
db-catalog-version=201306121
db-control-version=937
db-id=1
Automate generation of WAL and pg_control test files. The existing static files would not work with 32-bit or big-endian systems so create functions to generate these files dynamically rather than creating a bunch of new static files.
2017-11-19 03:02:54 +02:00
db-system-id=1000000000000000093
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
db-version="9.3"
[db:history]
Automate generation of WAL and pg_control test files. The existing static files would not work with 32-bit or big-endian systems so create functions to generate these files dynamically rather than creating a bunch of new static files.
2017-11-19 03:02:54 +02:00
1={"db-catalog-version":201306121,"db-control-version":937,"db-system-id":1000000000000000093,"db-version":"9.3"}
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
Improve performance of info file load/save. Info files required three copies in memory to be loaded (the original string, an ini representation, and the final info object). Not only was this memory inefficient but the Ini object does sequential scans when searching for keys making large files very slow to load. This has not been an issue since archive.info and backup.info are very small, but it becomes a big deal when loading manifests with hundreds of thousands of files. Instead of holding copies of the data in memory, use a callback to deliver the ini data directly to the object when loading. Use a similar method for save to avoid having an intermediate copy. Save is a bit complex because sections/keys must be written in alpha order or older versions of pgBackRest will not calculate the correct checksum. Also move the load retry logic to helper functions rather than embedding it in the Info object. This allows for more flexibility in loading and ensures that stack traces will be available when developing unit tests. Reviewed by Cynthia Shang.
2019-09-06 19:48:28 +02:00
[backrest]
backrest-checksum="[CHECKSUM]"
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
+ supplemental file: /archive/db/archive.info
---------------------------------------------
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
[backrest]
backrest-format=5
backrest-version="[VERSION-1]"
[db]
db-id=1
Automate generation of WAL and pg_control test files. The existing static files would not work with 32-bit or big-endian systems so create functions to generate these files dynamically rather than creating a bunch of new static files.
2017-11-19 03:02:54 +02:00
db-system-id=1000000000000000093
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
db-version="9.3"
[db:history]
Automate generation of WAL and pg_control test files. The existing static files would not work with 32-bit or big-endian systems so create functions to generate these files dynamically rather than creating a bunch of new static files.
2017-11-19 03:02:54 +02:00
1={"db-id":1000000000000000093,"db-version":"9.3"}
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
Improve performance of info file load/save. Info files required three copies in memory to be loaded (the original string, an ini representation, and the final info object). Not only was this memory inefficient but the Ini object does sequential scans when searching for keys making large files very slow to load. This has not been an issue since archive.info and backup.info are very small, but it becomes a big deal when loading manifests with hundreds of thousands of files. Instead of holding copies of the data in memory, use a callback to deliver the ini data directly to the object when loading. Use a similar method for save to avoid having an intermediate copy. Save is a bit complex because sections/keys must be written in alpha order or older versions of pgBackRest will not calculate the correct checksum. Also move the load retry logic to helper functions rather than embedding it in the Info object. This allows for more flexibility in loading and ensures that stack traces will be available when developing unit tests. Reviewed by Cynthia Shang.
2019-09-06 19:48:28 +02:00
[backrest]
backrest-checksum="[CHECKSUM]"
Rename most instances of master to primary in tests. This aligns better with general PostgreSQL usage and our own documentation (updated in 4bcef702). Usage in the backup.manifest tests has not been updated since it might break the file format.
2020-06-16 20:06:38 +02:00
stanza-upgrade db - already up to date (db-primary host)
> [CONTAINER-EXEC] db-primary [BACKREST-BIN] --config=[TEST_PATH]/db-primary/pgbackrest.conf --stanza=db --no-online stanza-upgrade
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
------------------------------------------------------------------------------------------------------------------------------------
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
P00 INFO: stanza-upgrade command begin [BACKREST-VERSION]: --buffer-size=[BUFFER-SIZE] --config=[TEST_PATH]/db-primary/pgbackrest.conf --db-timeout=45 --exec-id=[EXEC-ID] --lock-path=[TEST_PATH]/db-primary/lock --log-level-console=detail --log-level-file=[LOG-LEVEL-FILE] --log-level-stderr=off --log-path=[TEST_PATH]/db-primary/log[] --no-log-timestamp --no-online --pg1-path=[TEST_PATH]/db-primary/db/base --protocol-timeout=60 --repo1-gcs-bucket=gcsbucket --repo1-gcs-endpoint=gcs:4443 --repo1-gcs-key=<redacted> --repo1-gcs-key-type=token --repo1-path=/ --no-repo1-storage-verify-tls --repo1-type=gcs --stanza=db
Partial multi-repository implementation. Multi-repository implementations for the archive-push, check, info, stanza-create, stanza-upgrade, and stanza-delete commands. Multi-repo configuration is disabled so there should be no behavioral changes between these commands and their current single-repo implementations. Multi-repo documentation and integration tests are still in the multi-repo development branch. All unit tests work as multi-repo since they are able to bypass the configuration restrictions.
2021-01-21 22:21:50 +02:00
P00 INFO: stanza-upgrade for stanza 'db' on repo1
P00 INFO: stanza 'db' on repo1 is already up to date
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
P00 DETAIL: statistics: STATISTICS
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
P00 INFO: stanza-upgrade command end: completed successfully
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
+ supplemental file: /backup/db/backup.info
-------------------------------------------
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
[backrest]
backrest-format=5
backrest-version="[VERSION-1]"
[db]
db-catalog-version=201306121
db-control-version=937
db-id=1
Automate generation of WAL and pg_control test files. The existing static files would not work with 32-bit or big-endian systems so create functions to generate these files dynamically rather than creating a bunch of new static files.
2017-11-19 03:02:54 +02:00
db-system-id=1000000000000000093
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
db-version="9.3"
[db:history]
Automate generation of WAL and pg_control test files. The existing static files would not work with 32-bit or big-endian systems so create functions to generate these files dynamically rather than creating a bunch of new static files.
2017-11-19 03:02:54 +02:00
1={"db-catalog-version":201306121,"db-control-version":937,"db-system-id":1000000000000000093,"db-version":"9.3"}
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
Improve performance of info file load/save. Info files required three copies in memory to be loaded (the original string, an ini representation, and the final info object). Not only was this memory inefficient but the Ini object does sequential scans when searching for keys making large files very slow to load. This has not been an issue since archive.info and backup.info are very small, but it becomes a big deal when loading manifests with hundreds of thousands of files. Instead of holding copies of the data in memory, use a callback to deliver the ini data directly to the object when loading. Use a similar method for save to avoid having an intermediate copy. Save is a bit complex because sections/keys must be written in alpha order or older versions of pgBackRest will not calculate the correct checksum. Also move the load retry logic to helper functions rather than embedding it in the Info object. This allows for more flexibility in loading and ensures that stack traces will be available when developing unit tests. Reviewed by Cynthia Shang.
2019-09-06 19:48:28 +02:00
[backrest]
backrest-checksum="[CHECKSUM]"
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
+ supplemental file: /archive/db/archive.info
---------------------------------------------
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
[backrest]
backrest-format=5
backrest-version="[VERSION-1]"
[db]
db-id=1
Automate generation of WAL and pg_control test files. The existing static files would not work with 32-bit or big-endian systems so create functions to generate these files dynamically rather than creating a bunch of new static files.
2017-11-19 03:02:54 +02:00
db-system-id=1000000000000000093
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
db-version="9.3"
[db:history]
Automate generation of WAL and pg_control test files. The existing static files would not work with 32-bit or big-endian systems so create functions to generate these files dynamically rather than creating a bunch of new static files.
2017-11-19 03:02:54 +02:00
1={"db-id":1000000000000000093,"db-version":"9.3"}
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
Improve performance of info file load/save. Info files required three copies in memory to be loaded (the original string, an ini representation, and the final info object). Not only was this memory inefficient but the Ini object does sequential scans when searching for keys making large files very slow to load. This has not been an issue since archive.info and backup.info are very small, but it becomes a big deal when loading manifests with hundreds of thousands of files. Instead of holding copies of the data in memory, use a callback to deliver the ini data directly to the object when loading. Use a similar method for save to avoid having an intermediate copy. Save is a bit complex because sections/keys must be written in alpha order or older versions of pgBackRest will not calculate the correct checksum. Also move the load retry logic to helper functions rather than embedding it in the Info object. This allows for more flexibility in loading and ensures that stack traces will be available when developing unit tests. Reviewed by Cynthia Shang.
2019-09-06 19:48:28 +02:00
[backrest]
backrest-checksum="[CHECKSUM]"
Rename most instances of master to primary in tests. This aligns better with general PostgreSQL usage and our own documentation (updated in 4bcef702). Usage in the backup.manifest tests has not been updated since it might break the file format.
2020-06-16 20:06:38 +02:00
> [CONTAINER-EXEC] db-primary [BACKREST-BIN] --config=[TEST_PATH]/db-primary/pgbackrest.conf --stanza=db archive-push [TEST_PATH]/db-primary/db/base/pg_xlog/000000010000000100000001
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
------------------------------------------------------------------------------------------------------------------------------------
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
P00 INFO: archive-push command begin [BACKREST-VERSION]: [[TEST_PATH]/db-primary/db/base/pg_xlog/000000010000000100000001] --buffer-size=[BUFFER-SIZE] --compress-level=3 --compress-type=zst --config=[TEST_PATH]/db-primary/pgbackrest.conf --db-timeout=45 --exec-id=[EXEC-ID] --job-retry=0 --lock-path=[TEST_PATH]/db-primary/lock --log-level-console=detail --log-level-file=[LOG-LEVEL-FILE] --log-level-stderr=off --log-path=[TEST_PATH]/db-primary/log[] --no-log-timestamp --pg1-path=[TEST_PATH]/db-primary/db/base --protocol-timeout=60 --repo1-gcs-bucket=gcsbucket --repo1-gcs-endpoint=gcs:4443 --repo1-gcs-key=<redacted> --repo1-gcs-key-type=token --repo1-path=/ --no-repo1-storage-verify-tls --repo1-type=gcs --stanza=db
The archive-push command is implemented entirely in C. This new implementation should behave exactly like the old Perl code with the exception of updated log messages. Remove as much of the Perl code as possible without breaking other commands.
2019-03-29 15:26:33 +02:00
P00 INFO: pushed WAL file '000000010000000100000001' to the archive
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
P00 DETAIL: statistics: STATISTICS
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
P00 INFO: archive-push command end: completed successfully
Rename most instances of master to primary in tests. This aligns better with general PostgreSQL usage and our own documentation (updated in 4bcef702). Usage in the backup.manifest tests has not been updated since it might break the file format.
2020-06-16 20:06:38 +02:00
stanza-create db - fail on archive info file missing from non-empty dir (db-primary host)
> [CONTAINER-EXEC] db-primary [BACKREST-BIN] --config=[TEST_PATH]/db-primary/pgbackrest.conf --stanza=db --no-online stanza-create
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
------------------------------------------------------------------------------------------------------------------------------------
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
P00 INFO: stanza-create command begin [BACKREST-VERSION]: --buffer-size=[BUFFER-SIZE] --config=[TEST_PATH]/db-primary/pgbackrest.conf --db-timeout=45 --exec-id=[EXEC-ID] --lock-path=[TEST_PATH]/db-primary/lock --log-level-console=detail --log-level-file=[LOG-LEVEL-FILE] --log-level-stderr=off --log-path=[TEST_PATH]/db-primary/log[] --no-log-timestamp --no-online --pg1-path=[TEST_PATH]/db-primary/db/base --protocol-timeout=60 --repo1-gcs-bucket=gcsbucket --repo1-gcs-endpoint=gcs:4443 --repo1-gcs-key=<redacted> --repo1-gcs-key-type=token --repo1-path=/ --no-repo1-storage-verify-tls --repo1-type=gcs --stanza=db
Partial multi-repository implementation. Multi-repository implementations for the archive-push, check, info, stanza-create, stanza-upgrade, and stanza-delete commands. Multi-repo configuration is disabled so there should be no behavioral changes between these commands and their current single-repo implementations. Multi-repo documentation and integration tests are still in the multi-repo development branch. All unit tests work as multi-repo since they are able to bypass the configuration restrictions.
2021-01-21 22:21:50 +02:00
P00 INFO: stanza-create for stanza 'db' on repo1
P00 ERROR: [055]: backup.info exists but archive.info is missing on repo1
The stanza-create/update/delete commands are implemented entirely in C. Contributed by Cynthia Shang.
2019-08-21 22:26:28 +02:00
HINT: this may be a symptom of repository corruption!
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
P00 DETAIL: statistics: STATISTICS
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
P00 INFO: stanza-create command end: aborted with exception [055]
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
+ supplemental file: /backup/db/backup.info
-------------------------------------------
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
[backrest]
backrest-format=5
backrest-version="[VERSION-1]"
[db]
db-catalog-version=201306121
db-control-version=937
db-id=1
Automate generation of WAL and pg_control test files. The existing static files would not work with 32-bit or big-endian systems so create functions to generate these files dynamically rather than creating a bunch of new static files.
2017-11-19 03:02:54 +02:00
db-system-id=1000000000000000093
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
db-version="9.3"
[db:history]
Automate generation of WAL and pg_control test files. The existing static files would not work with 32-bit or big-endian systems so create functions to generate these files dynamically rather than creating a bunch of new static files.
2017-11-19 03:02:54 +02:00
1={"db-catalog-version":201306121,"db-control-version":937,"db-system-id":1000000000000000093,"db-version":"9.3"}
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
Improve performance of info file load/save. Info files required three copies in memory to be loaded (the original string, an ini representation, and the final info object). Not only was this memory inefficient but the Ini object does sequential scans when searching for keys making large files very slow to load. This has not been an issue since archive.info and backup.info are very small, but it becomes a big deal when loading manifests with hundreds of thousands of files. Instead of holding copies of the data in memory, use a callback to deliver the ini data directly to the object when loading. Use a similar method for save to avoid having an intermediate copy. Save is a bit complex because sections/keys must be written in alpha order or older versions of pgBackRest will not calculate the correct checksum. Also move the load retry logic to helper functions rather than embedding it in the Info object. This allows for more flexibility in loading and ensures that stack traces will be available when developing unit tests. Reviewed by Cynthia Shang.
2019-09-06 19:48:28 +02:00
[backrest]
backrest-checksum="[CHECKSUM]"
Rename most instances of master to primary in tests. This aligns better with general PostgreSQL usage and our own documentation (updated in 4bcef702). Usage in the backup.manifest tests has not been updated since it might break the file format.
2020-06-16 20:06:38 +02:00
> [CONTAINER-EXEC] db-primary [BACKREST-BIN] --config=[TEST_PATH]/db-primary/pgbackrest.conf --stanza=db archive-push [TEST_PATH]/db-primary/db/base/pg_xlog/000000010000000100000002
Fixed an issue retrieving WAL for old database versions. After a stanza-upgrade it should still be possible to restore backups from the previous version and perform recovery with archive-get. However, archive-get only checked the most recent db version/id and failed. Also clean up some issues when the same db version/id appears multiple times in the history. Fixed by Cynthia Shang. Reported by Clinton Adams.
2017-11-17 00:18:51 +02:00
------------------------------------------------------------------------------------------------------------------------------------
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
P00 INFO: archive-push command begin [BACKREST-VERSION]: [[TEST_PATH]/db-primary/db/base/pg_xlog/000000010000000100000002] --buffer-size=[BUFFER-SIZE] --compress-level=3 --compress-type=zst --config=[TEST_PATH]/db-primary/pgbackrest.conf --db-timeout=45 --exec-id=[EXEC-ID] --job-retry=0 --lock-path=[TEST_PATH]/db-primary/lock --log-level-console=detail --log-level-file=[LOG-LEVEL-FILE] --log-level-stderr=off --log-path=[TEST_PATH]/db-primary/log[] --no-log-timestamp --pg1-path=[TEST_PATH]/db-primary/db/base --protocol-timeout=60 --repo1-gcs-bucket=gcsbucket --repo1-gcs-endpoint=gcs:4443 --repo1-gcs-key=<redacted> --repo1-gcs-key-type=token --repo1-path=/ --no-repo1-storage-verify-tls --repo1-type=gcs --stanza=db
The archive-push command is implemented entirely in C. This new implementation should behave exactly like the old Perl code with the exception of updated log messages. Remove as much of the Perl code as possible without breaking other commands.
2019-03-29 15:26:33 +02:00
P00 INFO: pushed WAL file '000000010000000100000002' to the archive
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
P00 DETAIL: statistics: STATISTICS
Fixed an issue retrieving WAL for old database versions. After a stanza-upgrade it should still be possible to restore backups from the previous version and perform recovery with archive-get. However, archive-get only checked the most recent db version/id and failed. Also clean up some issues when the same db version/id appears multiple times in the history. Fixed by Cynthia Shang. Reported by Clinton Adams.
2017-11-17 00:18:51 +02:00
P00 INFO: archive-push command end: completed successfully
Rename most instances of master to primary in tests. This aligns better with general PostgreSQL usage and our own documentation (updated in 4bcef702). Usage in the backup.manifest tests has not been updated since it might break the file format.
2020-06-16 20:06:38 +02:00
> [CONTAINER-EXEC] db-primary [BACKREST-BIN] --config=[TEST_PATH]/db-primary/pgbackrest.conf --log-level-console=warn --archive-push-queue-max=33554432 --stanza=db archive-push [TEST_PATH]/db-primary/db/base/pg_xlog/000000010000000100000001
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
------------------------------------------------------------------------------------------------------------------------------------
Partial multi-repository implementation. Multi-repository implementations for the archive-push, check, info, stanza-create, stanza-upgrade, and stanza-delete commands. Multi-repo configuration is disabled so there should be no behavioral changes between these commands and their current single-repo implementations. Multi-repo documentation and integration tests are still in the multi-repo development branch. All unit tests work as multi-repo since they are able to bypass the configuration restrictions.
2021-01-21 22:21:50 +02:00
P00 ERROR: [044]: PostgreSQL version 9.4, system-id 1000000000000000094 do not match repo1 stanza version 9.3, system-id 1000000000000000093
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
HINT: are you archiving to the correct stanza?
Rename most instances of master to primary in tests. This aligns better with general PostgreSQL usage and our own documentation (updated in 4bcef702). Usage in the backup.manifest tests has not been updated since it might break the file format.
2020-06-16 20:06:38 +02:00
stanza-upgrade db - successful upgrade creates additional history (db-primary host)
> [CONTAINER-EXEC] db-primary [BACKREST-BIN] --config=[TEST_PATH]/db-primary/pgbackrest.conf --stanza=db --no-online stanza-upgrade
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
------------------------------------------------------------------------------------------------------------------------------------
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
P00 INFO: stanza-upgrade command begin [BACKREST-VERSION]: --buffer-size=[BUFFER-SIZE] --config=[TEST_PATH]/db-primary/pgbackrest.conf --db-timeout=45 --exec-id=[EXEC-ID] --lock-path=[TEST_PATH]/db-primary/lock --log-level-console=detail --log-level-file=[LOG-LEVEL-FILE] --log-level-stderr=off --log-path=[TEST_PATH]/db-primary/log[] --no-log-timestamp --no-online --pg1-path=[TEST_PATH]/db-primary/db/base --protocol-timeout=60 --repo1-gcs-bucket=gcsbucket --repo1-gcs-endpoint=gcs:4443 --repo1-gcs-key=<redacted> --repo1-gcs-key-type=token --repo1-path=/ --no-repo1-storage-verify-tls --repo1-type=gcs --stanza=db
Partial multi-repository implementation. Multi-repository implementations for the archive-push, check, info, stanza-create, stanza-upgrade, and stanza-delete commands. Multi-repo configuration is disabled so there should be no behavioral changes between these commands and their current single-repo implementations. Multi-repo documentation and integration tests are still in the multi-repo development branch. All unit tests work as multi-repo since they are able to bypass the configuration restrictions.
2021-01-21 22:21:50 +02:00
P00 INFO: stanza-upgrade for stanza 'db' on repo1
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
P00 DETAIL: statistics: STATISTICS
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
P00 INFO: stanza-upgrade command end: completed successfully
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
+ supplemental file: /backup/db/backup.info
-------------------------------------------
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
[backrest]
backrest-format=5
backrest-version="[VERSION-1]"
[db]
db-catalog-version=201409291
db-control-version=942
db-id=2
Automate generation of WAL and pg_control test files. The existing static files would not work with 32-bit or big-endian systems so create functions to generate these files dynamically rather than creating a bunch of new static files.
2017-11-19 03:02:54 +02:00
db-system-id=1000000000000000094
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
db-version="9.4"
[db:history]
Automate generation of WAL and pg_control test files. The existing static files would not work with 32-bit or big-endian systems so create functions to generate these files dynamically rather than creating a bunch of new static files.
2017-11-19 03:02:54 +02:00
1={"db-catalog-version":201306121,"db-control-version":937,"db-system-id":1000000000000000093,"db-version":"9.3"}
2={"db-catalog-version":201409291,"db-control-version":942,"db-system-id":1000000000000000094,"db-version":"9.4"}
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
Improve performance of info file load/save. Info files required three copies in memory to be loaded (the original string, an ini representation, and the final info object). Not only was this memory inefficient but the Ini object does sequential scans when searching for keys making large files very slow to load. This has not been an issue since archive.info and backup.info are very small, but it becomes a big deal when loading manifests with hundreds of thousands of files. Instead of holding copies of the data in memory, use a callback to deliver the ini data directly to the object when loading. Use a similar method for save to avoid having an intermediate copy. Save is a bit complex because sections/keys must be written in alpha order or older versions of pgBackRest will not calculate the correct checksum. Also move the load retry logic to helper functions rather than embedding it in the Info object. This allows for more flexibility in loading and ensures that stack traces will be available when developing unit tests. Reviewed by Cynthia Shang.
2019-09-06 19:48:28 +02:00
[backrest]
backrest-checksum="[CHECKSUM]"
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
+ supplemental file: /archive/db/archive.info
---------------------------------------------
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
[backrest]
backrest-format=5
backrest-version="[VERSION-1]"
[db]
db-id=2
Automate generation of WAL and pg_control test files. The existing static files would not work with 32-bit or big-endian systems so create functions to generate these files dynamically rather than creating a bunch of new static files.
2017-11-19 03:02:54 +02:00
db-system-id=1000000000000000094
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
db-version="9.4"
[db:history]
Automate generation of WAL and pg_control test files. The existing static files would not work with 32-bit or big-endian systems so create functions to generate these files dynamically rather than creating a bunch of new static files.
2017-11-19 03:02:54 +02:00
1={"db-id":1000000000000000093,"db-version":"9.3"}
2={"db-id":1000000000000000094,"db-version":"9.4"}
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
Improve performance of info file load/save. Info files required three copies in memory to be loaded (the original string, an ini representation, and the final info object). Not only was this memory inefficient but the Ini object does sequential scans when searching for keys making large files very slow to load. This has not been an issue since archive.info and backup.info are very small, but it becomes a big deal when loading manifests with hundreds of thousands of files. Instead of holding copies of the data in memory, use a callback to deliver the ini data directly to the object when loading. Use a similar method for save to avoid having an intermediate copy. Save is a bit complex because sections/keys must be written in alpha order or older versions of pgBackRest will not calculate the correct checksum. Also move the load retry logic to helper functions rather than embedding it in the Info object. This allows for more flexibility in loading and ensures that stack traces will be available when developing unit tests. Reviewed by Cynthia Shang.
2019-09-06 19:48:28 +02:00
[backrest]
backrest-checksum="[CHECKSUM]"
Rename most instances of master to primary in tests. This aligns better with general PostgreSQL usage and our own documentation (updated in 4bcef702). Usage in the backup.manifest tests has not been updated since it might break the file format.
2020-06-16 20:06:38 +02:00
> [CONTAINER-EXEC] db-primary [BACKREST-BIN] --config=[TEST_PATH]/db-primary/pgbackrest.conf --stanza=db archive-get 000000010000000100000002 [TEST_PATH]/db-primary/db/base/pg_xlog/RECOVERYXLOG
Fixed an issue retrieving WAL for old database versions. After a stanza-upgrade it should still be possible to restore backups from the previous version and perform recovery with archive-get. However, archive-get only checked the most recent db version/id and failed. Also clean up some issues when the same db version/id appears multiple times in the history. Fixed by Cynthia Shang. Reported by Clinton Adams.
2017-11-17 00:18:51 +02:00
------------------------------------------------------------------------------------------------------------------------------------
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
P00 INFO: archive-get command begin [BACKREST-VERSION]: [000000010000000100000002, [TEST_PATH]/db-primary/db/base/pg_xlog/RECOVERYXLOG] --buffer-size=[BUFFER-SIZE] --config=[TEST_PATH]/db-primary/pgbackrest.conf --db-timeout=45 --exec-id=[EXEC-ID] --job-retry=0 --lock-path=[TEST_PATH]/db-primary/lock --log-level-console=detail --log-level-file=[LOG-LEVEL-FILE] --log-level-stderr=off --log-path=[TEST_PATH]/db-primary/log[] --no-log-timestamp --pg1-path=[TEST_PATH]/db-primary/db/base --protocol-timeout=60 --repo1-gcs-bucket=gcsbucket --repo1-gcs-endpoint=gcs:4443 --repo1-gcs-key=<redacted> --repo1-gcs-key-type=token --repo1-path=/ --no-repo1-storage-verify-tls --repo1-type=gcs --stanza=db
Add archive-get command multi-repo support. Repositories will be searched in order for the requested archive file. Errors will be reported as warnings as long as a valid copy of the archive file is found.
2021-02-23 22:34:28 +02:00
P00 INFO: found 000000010000000100000002 in the repo1: 9.3-1 archive
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
P00 DETAIL: statistics: STATISTICS
Fixed an issue retrieving WAL for old database versions. After a stanza-upgrade it should still be possible to restore backups from the previous version and perform recovery with archive-get. However, archive-get only checked the most recent db version/id and failed. Also clean up some issues when the same db version/id appears multiple times in the history. Fixed by Cynthia Shang. Reported by Clinton Adams.
2017-11-17 00:18:51 +02:00
P00 INFO: archive-get command end: completed successfully
Rename most instances of master to primary in tests. This aligns better with general PostgreSQL usage and our own documentation (updated in 4bcef702). Usage in the backup.manifest tests has not been updated since it might break the file format.
2020-06-16 20:06:38 +02:00
> [CONTAINER-EXEC] db-primary [BACKREST-BIN] --config=[TEST_PATH]/db-primary/pgbackrest.conf --log-level-console=warn --archive-push-queue-max=33554432 --stanza=db archive-push [TEST_PATH]/db-primary/db/base/pg_xlog/000000010000000100000001
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
------------------------------------------------------------------------------------------------------------------------------------
Rename most instances of master to primary in tests. This aligns better with general PostgreSQL usage and our own documentation (updated in 4bcef702). Usage in the backup.manifest tests has not been updated since it might break the file format.
2020-06-16 20:06:38 +02:00
full backup - create first full backup (db-primary host)
Make --repo optional for backup command. If there are multiple repos and the --repo option is not specified then backup will automatically select the highest priority repo.
2021-02-26 21:49:50 +02:00
> [CONTAINER-EXEC] db-primary [BACKREST-BIN] --config=[TEST_PATH]/db-primary/pgbackrest.conf --repo1-retention-full=2 --no-online --type=full --stanza=db backup
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
------------------------------------------------------------------------------------------------------------------------------------
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
P00 INFO: backup command begin [BACKREST-VERSION]: --buffer-size=[BUFFER-SIZE] --compress-level=3 --compress-type=zst --config=[TEST_PATH]/db-primary/pgbackrest.conf --db-timeout=45 --exec-id=[EXEC-ID] --job-retry=0 --lock-path=[TEST_PATH]/db-primary/lock --log-level-console=detail --log-level-file=[LOG-LEVEL-FILE] --log-level-stderr=off --log-path=[TEST_PATH]/db-primary/log[] --no-log-timestamp --no-online --pg1-path=[TEST_PATH]/db-primary/db/base --protocol-timeout=60 --repo1-gcs-bucket=gcsbucket --repo1-gcs-endpoint=gcs:4443 --repo1-gcs-key=<redacted> --repo1-gcs-key-type=token --repo1-path=/ --repo1-retention-full=2 --no-repo1-storage-verify-tls --repo1-type=gcs --stanza=db --start-fast --type=full
Read segment size from WAL headers. This allows validation of the WAL segment size for PostgreSQL versions <= 10.
2020-07-09 23:32:36 +02:00
P01 INFO: backup file [TEST_PATH]/db-primary/db/base/pg_xlog/RECOVERYXLOG (16MB, 33%) checksum 51a8525d254c01f5edddda30b7fe697c7e44705c
P01 INFO: backup file [TEST_PATH]/db-primary/db/base/pg_xlog/000000010000000100000002 (16MB, 66%) checksum 51a8525d254c01f5edddda30b7fe697c7e44705c
P01 INFO: backup file [TEST_PATH]/db-primary/db/base/pg_xlog/000000010000000100000001 (16MB, 99%) checksum f92539dea1f9482e2946c1138eeeecdea29d7f19
Rename most instances of master to primary in tests. This aligns better with general PostgreSQL usage and our own documentation (updated in 4bcef702). Usage in the backup.manifest tests has not been updated since it might break the file format.
2020-06-16 20:06:38 +02:00
P01 INFO: backup file [TEST_PATH]/db-primary/db/base/global/pg_control (8KB, 100%) checksum 4c77c900f7af0d9ab13fa9982051a42e0b637f6c
P01 INFO: backup file [TEST_PATH]/db-primary/db/base/pg_xlog/archive_status/000000010000000100000002.ready (0B, 100%)
P01 INFO: backup file [TEST_PATH]/db-primary/db/base/pg_xlog/archive_status/000000010000000100000001.ready (0B, 100%)
Fixed an issue retrieving WAL for old database versions. After a stanza-upgrade it should still be possible to restore backups from the previous version and perform recovery with archive-get. However, archive-get only checked the most recent db version/id and failed. Also clean up some issues when the same db version/id appears multiple times in the history. Fixed by Cynthia Shang. Reported by Clinton Adams.
2017-11-17 00:18:51 +02:00
P00 INFO: full backup size = 48MB
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
P00 INFO: new backup label = [BACKUP-FULL-1]
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
P00 DETAIL: statistics: STATISTICS
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
P00 INFO: backup command end: completed successfully
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
P00 INFO: expire command begin [BACKREST-VERSION]: --buffer-size=[BUFFER-SIZE] --config=[TEST_PATH]/db-primary/pgbackrest.conf --exec-id=[EXEC-ID] --lock-path=[TEST_PATH]/db-primary/lock --log-level-console=detail --log-level-file=[LOG-LEVEL-FILE] --log-level-stderr=off --log-path=[TEST_PATH]/db-primary/log --no-log-timestamp --repo1-gcs-bucket=gcsbucket --repo1-gcs-endpoint=gcs:4443 --repo1-gcs-key=<redacted> --repo1-gcs-key-type=token --repo1-path=/ --repo1-retention-full=2 --no-repo1-storage-verify-tls --repo1-type=gcs --stanza=db
P00 DETAIL: statistics: STATISTICS
The stanza-create/update/delete commands are implemented entirely in C. Contributed by Cynthia Shang.
2019-08-21 22:26:28 +02:00
P00 INFO: expire command end: completed successfully
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
Rename most instances of master to primary in tests. This aligns better with general PostgreSQL usage and our own documentation (updated in 4bcef702). Usage in the backup.manifest tests has not been updated since it might break the file format.
2020-06-16 20:06:38 +02:00
+ supplemental file: [TEST_PATH]/db-primary/pgbackrest.conf
-----------------------------------------------------------
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
[db]
Rename most instances of master to primary in tests. This aligns better with general PostgreSQL usage and our own documentation (updated in 4bcef702). Usage in the backup.manifest tests has not been updated since it might break the file format.
2020-06-16 20:06:38 +02:00
pg1-path=[TEST_PATH]/db-primary/db/base
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
The stanza-create/update/delete commands are implemented entirely in C. Contributed by Cynthia Shang.
2019-08-21 22:26:28 +02:00
[global]
Integration test improvements for disk and memory efficiency. Set log-level-file=off when more that one test will run. In this case is it impossible to see the logs anyway since they will be automatically cleaned up after the test. This improves performance pretty dramatically since trace-level logging is expensive. If a singe integration test is run then log-level-file is trace by default but can be changed with the --log-level-test-file option. Reduce buffer-size to 64k to save memory during testing and allow more processes to run in parallel. Update log replacement rules so that these options can change without affecting expect logs.
2019-12-17 22:23:07 +02:00
buffer-size=[BUFFER-SIZE]
The stanza-create/update/delete commands are implemented entirely in C. Contributed by Cynthia Shang.
2019-08-21 22:26:28 +02:00
compress-level=3
Add Zstandard compression support. Zstandard is a fast lossless compression algorithm targeting real-time compression scenarios at zlib-level and better compression ratios. It's backed by a very fast entropy stage, provided by Huff0 and FSE library. Zstandard version >= 1.0 is required, which is generally only available on newer distributions.
2020-05-04 21:25:27 +02:00
compress-type=zst
The stanza-create/update/delete commands are implemented entirely in C. Contributed by Cynthia Shang.
2019-08-21 22:26:28 +02:00
db-timeout=45
Add job-retry and job-retry-interval options. These options specify the number of local worker job retries and the retry interval after one immediate retry. There is some value in allowing retries to be specified by the user but for the most part these options are for suppressing retries during testing, which can save a lot of time. The bug introduced in d1d25c7 and fixed in 8b86d5e also suggests it is better not to use retries in tests. Remove the default delayed retries for archive-get/archive-push, leaving only the immediate retry. These commands are retried by PostgreSQL so it doesn't make sense to do too many retries internally. These options are currently internal.
2021-01-11 22:15:25 +02:00
job-retry=0
Rename most instances of master to primary in tests. This aligns better with general PostgreSQL usage and our own documentation (updated in 4bcef702). Usage in the backup.manifest tests has not been updated since it might break the file format.
2020-06-16 20:06:38 +02:00
lock-path=[TEST_PATH]/db-primary/lock
The stanza-create/update/delete commands are implemented entirely in C. Contributed by Cynthia Shang.
2019-08-21 22:26:28 +02:00
log-level-console=detail
Integration test improvements for disk and memory efficiency. Set log-level-file=off when more that one test will run. In this case is it impossible to see the logs anyway since they will be automatically cleaned up after the test. This improves performance pretty dramatically since trace-level logging is expensive. If a singe integration test is run then log-level-file is trace by default but can be changed with the --log-level-test-file option. Reduce buffer-size to 64k to save memory during testing and allow more processes to run in parallel. Update log replacement rules so that these options can change without affecting expect logs.
2019-12-17 22:23:07 +02:00
log-level-file=[LOG-LEVEL-FILE]
The stanza-create/update/delete commands are implemented entirely in C. Contributed by Cynthia Shang.
2019-08-21 22:26:28 +02:00
log-level-stderr=off
Rename most instances of master to primary in tests. This aligns better with general PostgreSQL usage and our own documentation (updated in 4bcef702). Usage in the backup.manifest tests has not been updated since it might break the file format.
2020-06-16 20:06:38 +02:00
log-path=[TEST_PATH]/db-primary/log
Integration test improvements for disk and memory efficiency. Set log-level-file=off when more that one test will run. In this case is it impossible to see the logs anyway since they will be automatically cleaned up after the test. This improves performance pretty dramatically since trace-level logging is expensive. If a singe integration test is run then log-level-file is trace by default but can be changed with the --log-level-test-file option. Reduce buffer-size to 64k to save memory during testing and allow more processes to run in parallel. Update log replacement rules so that these options can change without affecting expect logs.
2019-12-17 22:23:07 +02:00
log-subprocess=[LOG-SUBPROCESS]
The stanza-create/update/delete commands are implemented entirely in C. Contributed by Cynthia Shang.
2019-08-21 22:26:28 +02:00
log-timestamp=n
protocol-timeout=60
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
repo1-gcs-bucket=gcsbucket
repo1-gcs-endpoint=gcs:4443
repo1-gcs-key=testkey
repo1-gcs-key-type=token
repo1-path=/
repo1-storage-verify-tls=n
repo1-type=gcs
Rename most instances of master to primary in tests. This aligns better with general PostgreSQL usage and our own documentation (updated in 4bcef702). Usage in the backup.manifest tests has not been updated since it might break the file format.
2020-06-16 20:06:38 +02:00
spool-path=[TEST_PATH]/db-primary/spool
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
The stanza-create/update/delete commands are implemented entirely in C. Contributed by Cynthia Shang.
2019-08-21 22:26:28 +02:00
[global:backup]
archive-copy=y
start-fast=y
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
Rename most instances of master to primary in tests. This aligns better with general PostgreSQL usage and our own documentation (updated in 4bcef702). Usage in the backup.manifest tests has not been updated since it might break the file format.
2020-06-16 20:06:38 +02:00
stanza-upgrade db - successfully upgrade (db-primary host)
> [CONTAINER-EXEC] db-primary [BACKREST-BIN] --config=[TEST_PATH]/db-primary/pgbackrest.conf --stanza=db --no-online stanza-upgrade
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
------------------------------------------------------------------------------------------------------------------------------------
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
P00 INFO: stanza-upgrade command begin [BACKREST-VERSION]: --buffer-size=[BUFFER-SIZE] --config=[TEST_PATH]/db-primary/pgbackrest.conf --db-timeout=45 --exec-id=[EXEC-ID] --lock-path=[TEST_PATH]/db-primary/lock --log-level-console=detail --log-level-file=[LOG-LEVEL-FILE] --log-level-stderr=off --log-path=[TEST_PATH]/db-primary/log[] --no-log-timestamp --no-online --pg1-path=[TEST_PATH]/db-primary/db/base --protocol-timeout=60 --repo1-gcs-bucket=gcsbucket --repo1-gcs-endpoint=gcs:4443 --repo1-gcs-key=<redacted> --repo1-gcs-key-type=token --repo1-path=/ --no-repo1-storage-verify-tls --repo1-type=gcs --stanza=db
Partial multi-repository implementation. Multi-repository implementations for the archive-push, check, info, stanza-create, stanza-upgrade, and stanza-delete commands. Multi-repo configuration is disabled so there should be no behavioral changes between these commands and their current single-repo implementations. Multi-repo documentation and integration tests are still in the multi-repo development branch. All unit tests work as multi-repo since they are able to bypass the configuration restrictions.
2021-01-21 22:21:50 +02:00
P00 INFO: stanza-upgrade for stanza 'db' on repo1
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
P00 DETAIL: statistics: STATISTICS
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
P00 INFO: stanza-upgrade command end: completed successfully
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
+ supplemental file: /backup/db/backup.info
-------------------------------------------
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
[backrest]
backrest-format=5
backrest-version="[VERSION-1]"
[backup:current]
Set archive-check option in manifest correctly when offline. Archive check does not run when in offline backup mode but the option was set to true in the manifest. It's harmless since these options are informational only but it could cause confusion when debugging.
2019-11-28 15:27:21 +02:00
[BACKUP-FULL-1]={"backrest-format":5,"backrest-version":"[VERSION-1]","backup-archive-start":null,"backup-archive-stop":null,"backup-info-repo-size":[SIZE],"backup-info-repo-size-delta":[DELTA],"backup-info-size":[SIZE],"backup-info-size-delta":[DELTA],"backup-timestamp-start":[TIMESTAMP],"backup-timestamp-stop":[TIMESTAMP],"backup-type":"full","db-id":2,"option-archive-check":false,"option-archive-copy":true,"option-backup-standby":false,"option-checksum-page":false,"option-compress":true,"option-hardlink":false,"option-online":false}
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
[db]
db-catalog-version=201510051
db-control-version=942
Error on db history mismatch when expiring. Amend commit 434cd832 to error when the db history in archive.info and backup.info do not match. The Perl code would attempt to reconcile the history by matching on system id and version but we are not planning to migrate that code to C. It's possible that there are users with mismatches but if so they should have been getting errors from info for the last six months. It's easy enough to manually fix these files if there are any mismatches in the field. Contributed by Cynthia Shang.
2019-06-24 17:59:44 +02:00
db-id=3
Automate generation of WAL and pg_control test files. The existing static files would not work with 32-bit or big-endian systems so create functions to generate these files dynamically rather than creating a bunch of new static files.
2017-11-19 03:02:54 +02:00
db-system-id=1000000000000000095
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
db-version="9.5"
[db:history]
Error on db history mismatch when expiring. Amend commit 434cd832 to error when the db history in archive.info and backup.info do not match. The Perl code would attempt to reconcile the history by matching on system id and version but we are not planning to migrate that code to C. It's possible that there are users with mismatches but if so they should have been getting errors from info for the last six months. It's easy enough to manually fix these files if there are any mismatches in the field. Contributed by Cynthia Shang.
2019-06-24 17:59:44 +02:00
1={"db-catalog-version":201306121,"db-control-version":937,"db-system-id":1000000000000000093,"db-version":"9.3"}
2={"db-catalog-version":201409291,"db-control-version":942,"db-system-id":1000000000000000094,"db-version":"9.4"}
3={"db-catalog-version":201510051,"db-control-version":942,"db-system-id":1000000000000000095,"db-version":"9.5"}
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
Improve performance of info file load/save. Info files required three copies in memory to be loaded (the original string, an ini representation, and the final info object). Not only was this memory inefficient but the Ini object does sequential scans when searching for keys making large files very slow to load. This has not been an issue since archive.info and backup.info are very small, but it becomes a big deal when loading manifests with hundreds of thousands of files. Instead of holding copies of the data in memory, use a callback to deliver the ini data directly to the object when loading. Use a similar method for save to avoid having an intermediate copy. Save is a bit complex because sections/keys must be written in alpha order or older versions of pgBackRest will not calculate the correct checksum. Also move the load retry logic to helper functions rather than embedding it in the Info object. This allows for more flexibility in loading and ensures that stack traces will be available when developing unit tests. Reviewed by Cynthia Shang.
2019-09-06 19:48:28 +02:00
[backrest]
backrest-checksum="[CHECKSUM]"
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
+ supplemental file: /archive/db/archive.info
---------------------------------------------
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
[backrest]
backrest-format=5
backrest-version="[VERSION-1]"
[db]
The stanza-create/update/delete commands are implemented entirely in C. Contributed by Cynthia Shang.
2019-08-21 22:26:28 +02:00
db-id=3
Automate generation of WAL and pg_control test files. The existing static files would not work with 32-bit or big-endian systems so create functions to generate these files dynamically rather than creating a bunch of new static files.
2017-11-19 03:02:54 +02:00
db-system-id=1000000000000000095
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
db-version="9.5"
[db:history]
Automate generation of WAL and pg_control test files. The existing static files would not work with 32-bit or big-endian systems so create functions to generate these files dynamically rather than creating a bunch of new static files.
2017-11-19 03:02:54 +02:00
1={"db-id":1000000000000000093,"db-version":"9.3"}
2={"db-id":1000000000000000094,"db-version":"9.4"}
The stanza-create/update/delete commands are implemented entirely in C. Contributed by Cynthia Shang.
2019-08-21 22:26:28 +02:00
3={"db-id":1000000000000000095,"db-version":"9.5"}
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
Improve performance of info file load/save. Info files required three copies in memory to be loaded (the original string, an ini representation, and the final info object). Not only was this memory inefficient but the Ini object does sequential scans when searching for keys making large files very slow to load. This has not been an issue since archive.info and backup.info are very small, but it becomes a big deal when loading manifests with hundreds of thousands of files. Instead of holding copies of the data in memory, use a callback to deliver the ini data directly to the object when loading. Use a similar method for save to avoid having an intermediate copy. Save is a bit complex because sections/keys must be written in alpha order or older versions of pgBackRest will not calculate the correct checksum. Also move the load retry logic to helper functions rather than embedding it in the Info object. This allows for more flexibility in loading and ensures that stack traces will be available when developing unit tests. Reviewed by Cynthia Shang.
2019-09-06 19:48:28 +02:00
[backrest]
backrest-checksum="[CHECKSUM]"
Rename most instances of master to primary in tests. This aligns better with general PostgreSQL usage and our own documentation (updated in 4bcef702). Usage in the backup.manifest tests has not been updated since it might break the file format.
2020-06-16 20:06:38 +02:00
stanza-upgrade db - upgrade fails with mismatched db-ids (db-primary host)
> [CONTAINER-EXEC] db-primary [BACKREST-BIN] --config=[TEST_PATH]/db-primary/pgbackrest.conf --stanza=db --no-online stanza-upgrade
Error on db history mismatch when expiring. Amend commit 434cd832 to error when the db history in archive.info and backup.info do not match. The Perl code would attempt to reconcile the history by matching on system id and version but we are not planning to migrate that code to C. It's possible that there are users with mismatches but if so they should have been getting errors from info for the last six months. It's easy enough to manually fix these files if there are any mismatches in the field. Contributed by Cynthia Shang.
2019-06-24 17:59:44 +02:00
------------------------------------------------------------------------------------------------------------------------------------
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
P00 INFO: stanza-upgrade command begin [BACKREST-VERSION]: --buffer-size=[BUFFER-SIZE] --config=[TEST_PATH]/db-primary/pgbackrest.conf --db-timeout=45 --exec-id=[EXEC-ID] --lock-path=[TEST_PATH]/db-primary/lock --log-level-console=detail --log-level-file=[LOG-LEVEL-FILE] --log-level-stderr=off --log-path=[TEST_PATH]/db-primary/log[] --no-log-timestamp --no-online --pg1-path=[TEST_PATH]/db-primary/db/base --protocol-timeout=60 --repo1-gcs-bucket=gcsbucket --repo1-gcs-endpoint=gcs:4443 --repo1-gcs-key=<redacted> --repo1-gcs-key-type=token --repo1-path=/ --no-repo1-storage-verify-tls --repo1-type=gcs --stanza=db
Partial multi-repository implementation. Multi-repository implementations for the archive-push, check, info, stanza-create, stanza-upgrade, and stanza-delete commands. Multi-repo configuration is disabled so there should be no behavioral changes between these commands and their current single-repo implementations. Multi-repo documentation and integration tests are still in the multi-repo development branch. All unit tests work as multi-repo since they are able to bypass the configuration restrictions.
2021-01-21 22:21:50 +02:00
P00 INFO: stanza-upgrade for stanza 'db' on repo1
The stanza-create/update/delete commands are implemented entirely in C. Contributed by Cynthia Shang.
2019-08-21 22:26:28 +02:00
P00 ERROR: [028]: backup info file and archive info file do not match
archive: id = 2, version = 9.5, system-id = 1000000000000000095
backup : id = 3, version = 9.5, system-id = 1000000000000000095
HINT: this may be a symptom of repository corruption!
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
P00 DETAIL: statistics: STATISTICS
The stanza-create/update/delete commands are implemented entirely in C. Contributed by Cynthia Shang.
2019-08-21 22:26:28 +02:00
P00 INFO: stanza-upgrade command end: aborted with exception [028]
Error on db history mismatch when expiring. Amend commit 434cd832 to error when the db history in archive.info and backup.info do not match. The Perl code would attempt to reconcile the history by matching on system id and version but we are not planning to migrate that code to C. It's possible that there are users with mismatches but if so they should have been getting errors from info for the last six months. It's easy enough to manually fix these files if there are any mismatches in the field. Contributed by Cynthia Shang.
2019-06-24 17:59:44 +02:00
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
+ supplemental file: /backup/db/backup.info
-------------------------------------------
Error on db history mismatch when expiring. Amend commit 434cd832 to error when the db history in archive.info and backup.info do not match. The Perl code would attempt to reconcile the history by matching on system id and version but we are not planning to migrate that code to C. It's possible that there are users with mismatches but if so they should have been getting errors from info for the last six months. It's easy enough to manually fix these files if there are any mismatches in the field. Contributed by Cynthia Shang.
2019-06-24 17:59:44 +02:00
[backrest]
backrest-format=5
backrest-version="[VERSION-1]"
[backup:current]
Set archive-check option in manifest correctly when offline. Archive check does not run when in offline backup mode but the option was set to true in the manifest. It's harmless since these options are informational only but it could cause confusion when debugging.
2019-11-28 15:27:21 +02:00
[BACKUP-FULL-1]={"backrest-format":5,"backrest-version":"[VERSION-1]","backup-archive-start":null,"backup-archive-stop":null,"backup-info-repo-size":[SIZE],"backup-info-repo-size-delta":[DELTA],"backup-info-size":[SIZE],"backup-info-size-delta":[DELTA],"backup-timestamp-start":[TIMESTAMP],"backup-timestamp-stop":[TIMESTAMP],"backup-type":"full","db-id":2,"option-archive-check":false,"option-archive-copy":true,"option-backup-standby":false,"option-checksum-page":false,"option-compress":true,"option-hardlink":false,"option-online":false}
Error on db history mismatch when expiring. Amend commit 434cd832 to error when the db history in archive.info and backup.info do not match. The Perl code would attempt to reconcile the history by matching on system id and version but we are not planning to migrate that code to C. It's possible that there are users with mismatches but if so they should have been getting errors from info for the last six months. It's easy enough to manually fix these files if there are any mismatches in the field. Contributed by Cynthia Shang.
2019-06-24 17:59:44 +02:00
[db]
db-catalog-version=201510051
db-control-version=942
db-id=3
db-system-id=1000000000000000095
db-version="9.5"
[db:history]
1={"db-catalog-version":201306121,"db-control-version":937,"db-system-id":1000000000000000093,"db-version":"9.3"}
2={"db-catalog-version":201409291,"db-control-version":942,"db-system-id":1000000000000000094,"db-version":"9.4"}
3={"db-catalog-version":201510051,"db-control-version":942,"db-system-id":1000000000000000095,"db-version":"9.5"}
Improve performance of info file load/save. Info files required three copies in memory to be loaded (the original string, an ini representation, and the final info object). Not only was this memory inefficient but the Ini object does sequential scans when searching for keys making large files very slow to load. This has not been an issue since archive.info and backup.info are very small, but it becomes a big deal when loading manifests with hundreds of thousands of files. Instead of holding copies of the data in memory, use a callback to deliver the ini data directly to the object when loading. Use a similar method for save to avoid having an intermediate copy. Save is a bit complex because sections/keys must be written in alpha order or older versions of pgBackRest will not calculate the correct checksum. Also move the load retry logic to helper functions rather than embedding it in the Info object. This allows for more flexibility in loading and ensures that stack traces will be available when developing unit tests. Reviewed by Cynthia Shang.
2019-09-06 19:48:28 +02:00
[backrest]
backrest-checksum="[CHECKSUM]"
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
+ supplemental file: /archive/db/archive.info
---------------------------------------------
Error on db history mismatch when expiring. Amend commit 434cd832 to error when the db history in archive.info and backup.info do not match. The Perl code would attempt to reconcile the history by matching on system id and version but we are not planning to migrate that code to C. It's possible that there are users with mismatches but if so they should have been getting errors from info for the last six months. It's easy enough to manually fix these files if there are any mismatches in the field. Contributed by Cynthia Shang.
2019-06-24 17:59:44 +02:00
[backrest]
backrest-format=5
backrest-version="[VERSION-1]"
[db]
The stanza-create/update/delete commands are implemented entirely in C. Contributed by Cynthia Shang.
2019-08-21 22:26:28 +02:00
db-id=1
db-system-id=1000000000000000093
db-version="9.3"
Error on db history mismatch when expiring. Amend commit 434cd832 to error when the db history in archive.info and backup.info do not match. The Perl code would attempt to reconcile the history by matching on system id and version but we are not planning to migrate that code to C. It's possible that there are users with mismatches but if so they should have been getting errors from info for the last six months. It's easy enough to manually fix these files if there are any mismatches in the field. Contributed by Cynthia Shang.
2019-06-24 17:59:44 +02:00
[db:history]
1={"db-id":1000000000000000093,"db-version":"9.3"}
Improve performance of info file load/save. Info files required three copies in memory to be loaded (the original string, an ini representation, and the final info object). Not only was this memory inefficient but the Ini object does sequential scans when searching for keys making large files very slow to load. This has not been an issue since archive.info and backup.info are very small, but it becomes a big deal when loading manifests with hundreds of thousands of files. Instead of holding copies of the data in memory, use a callback to deliver the ini data directly to the object when loading. Use a similar method for save to avoid having an intermediate copy. Save is a bit complex because sections/keys must be written in alpha order or older versions of pgBackRest will not calculate the correct checksum. Also move the load retry logic to helper functions rather than embedding it in the Info object. This allows for more flexibility in loading and ensures that stack traces will be available when developing unit tests. Reviewed by Cynthia Shang.
2019-09-06 19:48:28 +02:00
[backrest]
backrest-checksum="[CHECKSUM]"
Rename most instances of master to primary in tests. This aligns better with general PostgreSQL usage and our own documentation (updated in 4bcef702). Usage in the backup.manifest tests has not been updated since it might break the file format.
2020-06-16 20:06:38 +02:00
> [CONTAINER-EXEC] db-primary [BACKREST-BIN] --config=[TEST_PATH]/db-primary/pgbackrest.conf --log-level-console=warn --archive-push-queue-max=33554432 --stanza=db archive-push [TEST_PATH]/db-primary/db/base/pg_xlog/000000010000000100000001
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
------------------------------------------------------------------------------------------------------------------------------------
Rename most instances of master to primary in tests. This aligns better with general PostgreSQL usage and our own documentation (updated in 4bcef702). Usage in the backup.manifest tests has not been updated since it might break the file format.
2020-06-16 20:06:38 +02:00
diff backup - diff changed to full backup (db-primary host)
Make --repo optional for backup command. If there are multiple repos and the --repo option is not specified then backup will automatically select the highest priority repo.
2021-02-26 21:49:50 +02:00
> [CONTAINER-EXEC] db-primary [BACKREST-BIN] --config=[TEST_PATH]/db-primary/pgbackrest.conf --repo1-retention-full=2 --no-online --type=diff --stanza=db backup
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
------------------------------------------------------------------------------------------------------------------------------------
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
P00 INFO: backup command begin [BACKREST-VERSION]: --buffer-size=[BUFFER-SIZE] --compress-level=3 --compress-type=zst --config=[TEST_PATH]/db-primary/pgbackrest.conf --db-timeout=45 --exec-id=[EXEC-ID] --job-retry=0 --lock-path=[TEST_PATH]/db-primary/lock --log-level-console=detail --log-level-file=[LOG-LEVEL-FILE] --log-level-stderr=off --log-path=[TEST_PATH]/db-primary/log[] --no-log-timestamp --no-online --pg1-path=[TEST_PATH]/db-primary/db/base --protocol-timeout=60 --repo1-gcs-bucket=gcsbucket --repo1-gcs-endpoint=gcs:4443 --repo1-gcs-key=<redacted> --repo1-gcs-key-type=token --repo1-path=/ --repo1-retention-full=2 --no-repo1-storage-verify-tls --repo1-type=gcs --stanza=db --start-fast --type=diff
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
P00 WARN: no prior backup exists, diff backup has been changed to full
Read segment size from WAL headers. This allows validation of the WAL segment size for PostgreSQL versions <= 10.
2020-07-09 23:32:36 +02:00
P01 INFO: backup file [TEST_PATH]/db-primary/db/base/pg_xlog/RECOVERYXLOG (16MB, 33%) checksum 51a8525d254c01f5edddda30b7fe697c7e44705c
P01 INFO: backup file [TEST_PATH]/db-primary/db/base/pg_xlog/000000010000000100000002 (16MB, 66%) checksum 51a8525d254c01f5edddda30b7fe697c7e44705c
P01 INFO: backup file [TEST_PATH]/db-primary/db/base/pg_xlog/000000010000000100000001 (16MB, 99%) checksum 762dae884fdccb805c5f3283662ea0f8da55f228
Rename most instances of master to primary in tests. This aligns better with general PostgreSQL usage and our own documentation (updated in 4bcef702). Usage in the backup.manifest tests has not been updated since it might break the file format.
2020-06-16 20:06:38 +02:00
P01 INFO: backup file [TEST_PATH]/db-primary/db/base/global/pg_control (8KB, 100%) checksum 4969435f3b36bfaa0f5a486bef97f1988a135520
P01 INFO: backup file [TEST_PATH]/db-primary/db/base/pg_xlog/archive_status/000000010000000100000002.ready (0B, 100%)
P01 INFO: backup file [TEST_PATH]/db-primary/db/base/pg_xlog/archive_status/000000010000000100000001.ready (0B, 100%)
Fixed an issue retrieving WAL for old database versions. After a stanza-upgrade it should still be possible to restore backups from the previous version and perform recovery with archive-get. However, archive-get only checked the most recent db version/id and failed. Also clean up some issues when the same db version/id appears multiple times in the history. Fixed by Cynthia Shang. Reported by Clinton Adams.
2017-11-17 00:18:51 +02:00
P00 INFO: full backup size = 48MB
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
P00 INFO: new backup label = [BACKUP-FULL-2]
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
P00 DETAIL: statistics: STATISTICS
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
P00 INFO: backup command end: completed successfully
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
P00 INFO: expire command begin [BACKREST-VERSION]: --buffer-size=[BUFFER-SIZE] --config=[TEST_PATH]/db-primary/pgbackrest.conf --exec-id=[EXEC-ID] --lock-path=[TEST_PATH]/db-primary/lock --log-level-console=detail --log-level-file=[LOG-LEVEL-FILE] --log-level-stderr=off --log-path=[TEST_PATH]/db-primary/log --no-log-timestamp --repo1-gcs-bucket=gcsbucket --repo1-gcs-endpoint=gcs:4443 --repo1-gcs-key=<redacted> --repo1-gcs-key-type=token --repo1-path=/ --repo1-retention-full=2 --no-repo1-storage-verify-tls --repo1-type=gcs --stanza=db
P00 INFO: repo1: remove archive path /archive/db/9.3-1
P00 DETAIL: statistics: STATISTICS
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
P00 INFO: expire command end: completed successfully
Rename most instances of master to primary in tests. This aligns better with general PostgreSQL usage and our own documentation (updated in 4bcef702). Usage in the backup.manifest tests has not been updated since it might break the file format.
2020-06-16 20:06:38 +02:00
+ supplemental file: [TEST_PATH]/db-primary/pgbackrest.conf
-----------------------------------------------------------
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
[db]
Rename most instances of master to primary in tests. This aligns better with general PostgreSQL usage and our own documentation (updated in 4bcef702). Usage in the backup.manifest tests has not been updated since it might break the file format.
2020-06-16 20:06:38 +02:00
pg1-path=[TEST_PATH]/db-primary/db/base
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
[global]
Integration test improvements for disk and memory efficiency. Set log-level-file=off when more that one test will run. In this case is it impossible to see the logs anyway since they will be automatically cleaned up after the test. This improves performance pretty dramatically since trace-level logging is expensive. If a singe integration test is run then log-level-file is trace by default but can be changed with the --log-level-test-file option. Reduce buffer-size to 64k to save memory during testing and allow more processes to run in parallel. Update log replacement rules so that these options can change without affecting expect logs.
2019-12-17 22:23:07 +02:00
buffer-size=[BUFFER-SIZE]
Fix custom settings for compress-level option being ignored. Reported by Jens Wilke.
2017-10-23 00:05:46 +02:00
compress-level=3
Add Zstandard compression support. Zstandard is a fast lossless compression algorithm targeting real-time compression scenarios at zlib-level and better compression ratios. It's backed by a very fast entropy stage, provided by Huff0 and FSE library. Zstandard version >= 1.0 is required, which is generally only available on newer distributions.
2020-05-04 21:25:27 +02:00
compress-type=zst
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
db-timeout=45
Add job-retry and job-retry-interval options. These options specify the number of local worker job retries and the retry interval after one immediate retry. There is some value in allowing retries to be specified by the user but for the most part these options are for suppressing retries during testing, which can save a lot of time. The bug introduced in d1d25c7 and fixed in 8b86d5e also suggests it is better not to use retries in tests. Remove the default delayed retries for archive-get/archive-push, leaving only the immediate retry. These commands are retried by PostgreSQL so it doesn't make sense to do too many retries internally. These options are currently internal.
2021-01-11 22:15:25 +02:00
job-retry=0
Rename most instances of master to primary in tests. This aligns better with general PostgreSQL usage and our own documentation (updated in 4bcef702). Usage in the backup.manifest tests has not been updated since it might break the file format.
2020-06-16 20:06:38 +02:00
lock-path=[TEST_PATH]/db-primary/lock
Reduce expect log level in mock/stanza tests. The expect tests were originally a rough-and-ready type of unit test so monitoring changes in the expect log helped us detect changes in behavior. Now the stanza code is heavily unit-tested so the detailed logs mainly cause churn and don't have any measurable benefit. Reduce the log level to DETAIL to make the logs less verbose and volatile, yet still check user-facing log messages.
2019-02-24 06:55:59 +02:00
log-level-console=detail
Integration test improvements for disk and memory efficiency. Set log-level-file=off when more that one test will run. In this case is it impossible to see the logs anyway since they will be automatically cleaned up after the test. This improves performance pretty dramatically since trace-level logging is expensive. If a singe integration test is run then log-level-file is trace by default but can be changed with the --log-level-test-file option. Reduce buffer-size to 64k to save memory during testing and allow more processes to run in parallel. Update log replacement rules so that these options can change without affecting expect logs.
2019-12-17 22:23:07 +02:00
log-level-file=[LOG-LEVEL-FILE]
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
log-level-stderr=off
Rename most instances of master to primary in tests. This aligns better with general PostgreSQL usage and our own documentation (updated in 4bcef702). Usage in the backup.manifest tests has not been updated since it might break the file format.
2020-06-16 20:06:38 +02:00
log-path=[TEST_PATH]/db-primary/log
Integration test improvements for disk and memory efficiency. Set log-level-file=off when more that one test will run. In this case is it impossible to see the logs anyway since they will be automatically cleaned up after the test. This improves performance pretty dramatically since trace-level logging is expensive. If a singe integration test is run then log-level-file is trace by default but can be changed with the --log-level-test-file option. Reduce buffer-size to 64k to save memory during testing and allow more processes to run in parallel. Update log replacement rules so that these options can change without affecting expect logs.
2019-12-17 22:23:07 +02:00
log-subprocess=[LOG-SUBPROCESS]
Set log-timestamp=n for integration tests. This means less filtering of logs needs to be done and new timestamps can be added without adding new filters.
2018-05-11 17:24:38 +02:00
log-timestamp=n
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
protocol-timeout=60
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
repo1-gcs-bucket=gcsbucket
repo1-gcs-endpoint=gcs:4443
repo1-gcs-key=testkey
repo1-gcs-key-type=token
repo1-path=/
repo1-storage-verify-tls=n
repo1-type=gcs
Rename most instances of master to primary in tests. This aligns better with general PostgreSQL usage and our own documentation (updated in 4bcef702). Usage in the backup.manifest tests has not been updated since it might break the file format.
2020-06-16 20:06:38 +02:00
spool-path=[TEST_PATH]/db-primary/spool
Consolidate stanza-create and stanza-upgrade tests into new stanza test. Contributed by Cynthia Shang.
2017-08-04 22:10:51 +02:00
[global:backup]
archive-copy=y
start-fast=y
Rename most instances of master to primary in tests. This aligns better with general PostgreSQL usage and our own documentation (updated in 4bcef702). Usage in the backup.manifest tests has not been updated since it might break the file format.
2020-06-16 20:06:38 +02:00
stanza-delete db - fail on missing stop file (db-primary host)
Partial multi-repository implementation. Multi-repository implementations for the archive-push, check, info, stanza-create, stanza-upgrade, and stanza-delete commands. Multi-repo configuration is disabled so there should be no behavioral changes between these commands and their current single-repo implementations. Multi-repo documentation and integration tests are still in the multi-repo development branch. All unit tests work as multi-repo since they are able to bypass the configuration restrictions.
2021-01-21 22:21:50 +02:00
> [CONTAINER-EXEC] db-primary [BACKREST-BIN] --config=[TEST_PATH]/db-primary/pgbackrest.conf --repo=1 --stanza=db stanza-delete
Add stanza-delete command to cleanup unused stanzas. Contributed by Cynthia Shang.
2018-01-03 19:23:33 +02:00
------------------------------------------------------------------------------------------------------------------------------------
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
P00 INFO: stanza-delete command begin [BACKREST-VERSION]: --buffer-size=[BUFFER-SIZE] --config=[TEST_PATH]/db-primary/pgbackrest.conf --db-timeout=45 --exec-id=[EXEC-ID] --lock-path=[TEST_PATH]/db-primary/lock --log-level-console=detail --log-level-file=[LOG-LEVEL-FILE] --log-level-stderr=off --log-path=[TEST_PATH]/db-primary/log[] --no-log-timestamp --pg1-path=[TEST_PATH]/db-primary/db/base --protocol-timeout=60 --repo=1 --repo1-gcs-bucket=gcsbucket --repo1-gcs-endpoint=gcs:4443 --repo1-gcs-key=<redacted> --repo1-gcs-key-type=token --repo1-path=/ --no-repo1-storage-verify-tls --repo1-type=gcs --stanza=db
Add stanza-delete command to cleanup unused stanzas. Contributed by Cynthia Shang.
2018-01-03 19:23:33 +02:00
P00 ERROR: [055]: stop file does not exist for stanza 'db'
The stanza-create/update/delete commands are implemented entirely in C. Contributed by Cynthia Shang.
2019-08-21 22:26:28 +02:00
HINT: has the pgbackrest stop command been run on this server for this stanza?
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
P00 DETAIL: statistics: STATISTICS
Add stanza-delete command to cleanup unused stanzas. Contributed by Cynthia Shang.
2018-01-03 19:23:33 +02:00
P00 INFO: stanza-delete command end: aborted with exception [055]
db must not exist for successful delete
Use minio for integration testing. ScalityS3 has not received any maintenance in years and is slow to start which is bad for testing. Replace it with minio which starts quickly and ships as a single executable or a tiny container. Minio has stricter limits on allowable characters but should still provide enough coverage to show that our encoding is working correctly. This commit also includes the upgrade to openssl 1.1.1 in the Ubuntu 18.04 container.
2019-07-03 04:20:35 +02:00
> list backup
Add stanza-delete command to cleanup unused stanzas. Contributed by Cynthia Shang.
2018-01-03 19:23:33 +02:00
------------------------------------------------------------------------------------------------------------------------------------
db
db must not exist for successful delete
Use minio for integration testing. ScalityS3 has not received any maintenance in years and is slow to start which is bad for testing. Replace it with minio which starts quickly and ships as a single executable or a tiny container. Minio has stricter limits on allowable characters but should still provide enough coverage to show that our encoding is working correctly. This commit also includes the upgrade to openssl 1.1.1 in the Ubuntu 18.04 container.
2019-07-03 04:20:35 +02:00
> list archive
Add stanza-delete command to cleanup unused stanzas. Contributed by Cynthia Shang.
2018-01-03 19:23:33 +02:00
------------------------------------------------------------------------------------------------------------------------------------
db
Rename most instances of master to primary in tests. This aligns better with general PostgreSQL usage and our own documentation (updated in 4bcef702). Usage in the backup.manifest tests has not been updated since it might break the file format.
2020-06-16 20:06:38 +02:00
stop db stanza (db-primary host)
> [CONTAINER-EXEC] db-primary [BACKREST-BIN] --config=[TEST_PATH]/db-primary/pgbackrest.conf --stanza=db stop
Add stanza-delete command to cleanup unused stanzas. Contributed by Cynthia Shang.
2018-01-03 19:23:33 +02:00
------------------------------------------------------------------------------------------------------------------------------------
Audit options valid for start/stop commands.
2020-12-31 18:10:48 +02:00
P00 INFO: stop command begin [BACKREST-VERSION]: --config=[TEST_PATH]/db-primary/pgbackrest.conf --exec-id=[EXEC-ID] --lock-path=[TEST_PATH]/db-primary/lock --log-level-console=detail --log-level-file=[LOG-LEVEL-FILE] --log-level-stderr=off --log-path=[TEST_PATH]/db-primary/log --no-log-timestamp --stanza=db
Add stanza-delete command to cleanup unused stanzas. Contributed by Cynthia Shang.
2018-01-03 19:23:33 +02:00
P00 INFO: stop command end: completed successfully
Rename most instances of master to primary in tests. This aligns better with general PostgreSQL usage and our own documentation (updated in 4bcef702). Usage in the backup.manifest tests has not been updated since it might break the file format.
2020-06-16 20:06:38 +02:00
stanza-delete db - successfully delete the stanza (db-primary host)
Partial multi-repository implementation. Multi-repository implementations for the archive-push, check, info, stanza-create, stanza-upgrade, and stanza-delete commands. Multi-repo configuration is disabled so there should be no behavioral changes between these commands and their current single-repo implementations. Multi-repo documentation and integration tests are still in the multi-repo development branch. All unit tests work as multi-repo since they are able to bypass the configuration restrictions.
2021-01-21 22:21:50 +02:00
> [CONTAINER-EXEC] db-primary [BACKREST-BIN] --config=[TEST_PATH]/db-primary/pgbackrest.conf --repo=1 --stanza=db stanza-delete
Add stanza-delete command to cleanup unused stanzas. Contributed by Cynthia Shang.
2018-01-03 19:23:33 +02:00
------------------------------------------------------------------------------------------------------------------------------------
GCS support for repository storage. GCS and GCS-compatible object stores can now be used for repository storage.
2021-03-05 19:13:51 +02:00
P00 INFO: stanza-delete command begin [BACKREST-VERSION]: --buffer-size=[BUFFER-SIZE] --config=[TEST_PATH]/db-primary/pgbackrest.conf --db-timeout=45 --exec-id=[EXEC-ID] --lock-path=[TEST_PATH]/db-primary/lock --log-level-console=detail --log-level-file=[LOG-LEVEL-FILE] --log-level-stderr=off --log-path=[TEST_PATH]/db-primary/log[] --no-log-timestamp --pg1-path=[TEST_PATH]/db-primary/db/base --protocol-timeout=60 --repo=1 --repo1-gcs-bucket=gcsbucket --repo1-gcs-endpoint=gcs:4443 --repo1-gcs-key=<redacted> --repo1-gcs-key-type=token --repo1-path=/ --no-repo1-storage-verify-tls --repo1-type=gcs --stanza=db
P00 DETAIL: statistics: STATISTICS
Add stanza-delete command to cleanup unused stanzas. Contributed by Cynthia Shang.
2018-01-03 19:23:33 +02:00
P00 INFO: stanza-delete command end: completed successfully
db must not exist for successful delete
Use minio for integration testing. ScalityS3 has not received any maintenance in years and is slow to start which is bad for testing. Replace it with minio which starts quickly and ships as a single executable or a tiny container. Minio has stricter limits on allowable characters but should still provide enough coverage to show that our encoding is working correctly. This commit also includes the upgrade to openssl 1.1.1 in the Ubuntu 18.04 container.
2019-07-03 04:20:35 +02:00
> list backup
Add stanza-delete command to cleanup unused stanzas. Contributed by Cynthia Shang.
2018-01-03 19:23:33 +02:00
------------------------------------------------------------------------------------------------------------------------------------
db must not exist for successful delete
Use minio for integration testing. ScalityS3 has not received any maintenance in years and is slow to start which is bad for testing. Replace it with minio which starts quickly and ships as a single executable or a tiny container. Minio has stricter limits on allowable characters but should still provide enough coverage to show that our encoding is working correctly. This commit also includes the upgrade to openssl 1.1.1 in the Ubuntu 18.04 container.
2019-07-03 04:20:35 +02:00
> list archive
Add stanza-delete command to cleanup unused stanzas. Contributed by Cynthia Shang.
2018-01-03 19:23:33 +02:00
------------------------------------------------------------------------------------------------------------------------------------
Reference in New Issue Copy Permalink