pg_probackup 2.2.3 released
Grigory Smolkin <[email protected]> Wed, 16 Oct 2019 20:14:04 +0300
| Newsgroups | gmane.comp.db.postgresql.announce |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format.
--------------543EDB2C8470E2691517F12E
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Postgres Professional are proud to announce the release of pg_probackup
2.2.3.
pg_probackup is a utility to manage backup and recovery of PostgreSQL
database cluster. It is designed to perform periodic full and
incremental page-level backups of the PostgreSQL instance that enable
you to restore the server in case of a failure.
Notable changes since 2.1.5
Major bugfix:
* The writing of metadata file containing the list of files belonging to
a backup was bugged, which resulted in losing the information about one
file per 4MB of metadata. Now the writing of metadata is done
correctly.The "validate" command can detect metadata corruption in
backups produced by affected versions. Affected versions: 2.1.4, 2.1.5
and 2.2.1. Reported by Leonid Kraubner. More information can be found
here: https://github.com/postgrespro/pg_probackup/issues/132
Bugfixes:
* WAL purge now has timeline awareness, previously it was possible for
WAL purge to unintentionally delete branched child timelines.
* Merge of compressed backups on multiple threads now works correctly.
* Handling of invalid stop_lsn is improved.
* SIGTERM and SIGINT signals are now handled correctly.
* If "--recovery-target=immediate" option is used during restore then
"recovery.conf" file is generated.
* After-backup validation now correctly reports the detected corruption.
* The backup attribute "recovery-xid" is calculated correctly now.
* Non-ISO datestyle formats in PostgreSQL cluster are now handled
correctly during backup.
* WAL archive purge now works as expected even if oldest backup on WAL
timeline has invalid status.
* Invalid backups are treated correctly by retention purge now,
previously they were aggressively deleted.
* Previously timeout for WAL streaming was always equal to zero, now its
value depends on "--archive-timeout" parameter.
* Previously using the "--recovery-target-lsn" option with "validate"
command was leading to validation of all backups instead of PITR validation.
* Now only valid backups can be choosen for PITR and validation of PITR
if backup ID is not specified.
New features:
* WAL archive catalog. Now it is possible to view the state of every WAL
timeline in archive.
* Backup Pinning. Now it is possible to exclude a backup from
established retention policy or, in other words, "pin" it for a
specified amount of time.
* WAL archive retention. Now it is possible to set the "depth" of WAL
stored in archive measured in backups per timeline.
* Partial restore. Now it is possible to restore only the specified
databases or exclude the specified databases from restore.
For more details can be found in the release notes:
https://github.com/postgrespro/pg_probackup/releases/tag/2.2.1
Download
--------
https://github.com/postgrespro/pg_probackup
--
Grigory Smolkin
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
--------------543EDB2C8470E2691517F12E
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Postgres Professional are proud to announce the release of
pg_probackup 2.2.3.<br>
<br>
pg_probackup is a utility to manage backup and recovery of
PostgreSQL database cluster. It is designed to perform periodic full
and incremental page-level backups of the PostgreSQL instance that
enable you to restore the server in case of a failure.<br>
<br>
Notable changes since 2.1.5<br>
<br>
Major bugfix:<br>
* <span style="color: rgb(36, 41, 46); font-size: 16px; font-style:
normal; font-variant-ligatures: normal; font-variant-caps: normal;
font-weight: 400; letter-spacing: normal; text-align: left;
text-indent: 0px; text-transform: none; white-space: normal;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255); text-decoration-style:
initial; text-decoration-color: initial; display: inline
!important; float: none;"><span></span>The writing of metadata
file containing the list of files belonging to a backup was
bugged, which resulted in losing the information about one file
per 4MB of metadata. Now the writing of metadata is done
correctly.</span><span style="color: rgb(36, 41, 46); font-size:
16px; font-style: normal; font-variant-ligatures: normal;
font-variant-caps: normal; font-weight: 400; letter-spacing:
normal; text-align: left; text-indent: 0px; text-transform: none;
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width:
0px; background-color: rgb(255, 255, 255); text-decoration-style:
initial; text-decoration-color: initial; display: inline
!important; float: none;"> The "validate" command can detect
metadata corruption in backups produced by affected versions.
Affected versions: 2.1.4, 2.1.5 and 2.2.1. Reported by Leonid
Kraubner. More information can be found here: </span><a
href="https://github.com/postgrespro/pg_probackup/issues/132">https://github.com/postgrespro/pg_probackup/issues/132</a><br>
<br>
Bugfixes:<br>
* <span style="color: rgb(36, 41, 46); font-size: 16px; font-style:
normal; font-variant-ligatures: normal; font-variant-caps: normal;
font-weight: 400; letter-spacing: normal; text-align: left;
text-indent: 0px; text-transform: none; white-space: normal;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255); text-decoration-style:
initial; text-decoration-color: initial; display: inline
!important; float: none;">WAL purge now has timeline awareness,
previously it was possible for WAL purge to unintentionally delete
branched child timelines.<br>
* </span><span style="color: rgb(36, 41, 46); font-size: 16px;
font-style: normal; font-variant-ligatures: normal;
font-variant-caps: normal; font-weight: 400; letter-spacing:
normal; text-align: left; text-indent: 0px; text-transform: none;
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width:
0px; background-color: rgb(255, 255, 255); text-decoration-style:
initial; text-decoration-color: initial; display: inline
!important; float: none;">Merge of compressed backups on multiple
threads now works correctly.<br>
* </span><span style="color: rgb(36, 41, 46); font-size: 16px;
font-style: normal; font-variant-ligatures: normal;
font-variant-caps: normal; font-weight: 400; letter-spacing:
normal; text-align: left; text-indent: 0px; text-transform: none;
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width:
0px; background-color: rgb(255, 255, 255); text-decoration-style:
initial; text-decoration-color: initial; display: inline
!important; float: none;">Handling of invalid stop_lsn is
improved.</span><br>
* <span style="color: rgb(36, 41, 46); font-size: 16px; font-style:
normal; font-variant-ligatures: normal; font-variant-caps: normal;
font-weight: 400; letter-spacing: normal; text-align: left;
text-indent: 0px; text-transform: none; white-space: normal;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255); text-decoration-style:
initial; text-decoration-color: initial; display: inline
!important; float: none;">SIGTERM and SIGINT signals are now
handled correctly.<br>
* </span><span style="color: rgb(36, 41, 46); font-size: 16px;
font-style: normal; font-variant-ligatures: normal;
font-variant-caps: normal; font-weight: 400; letter-spacing:
normal; text-align: left; text-indent: 0px; text-transform: none;
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width:
0px; background-color: rgb(255, 255, 255); text-decoration-style:
initial; text-decoration-color: initial; display: inline
!important; float: none;"><span style="color: rgb(36, 41, 46);
font-size: 16px; font-style: normal; font-variant-ligatures:
normal; font-variant-caps: normal; font-weight: 400;
letter-spacing: normal; text-align: left; text-indent: 0px;
text-transform: none; white-space: normal; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(255, 255,
255); text-decoration-style: initial; text-decoration-color:
initial; display: inline !important; float: none;">If
"--recovery-target=immediate" option is used during restore then
"</span>recovery.conf" file is generated.<br>
* After-backup validation now correctly reports the detected
corruption.<br>
* The backup attribute "recovery-xid" is calculated correctly now.<br>
* Non-ISO datestyle formats in PostgreSQL cluster are now handled
correctly during backup.<br>
* WAL archive purge now works as expected even if oldest backup on
WAL timeline has invalid status.<br>
* Invalid backups are treated correctly by </span><span
style="color: rgb(36, 41, 46); font-size: 16px; font-style:
normal; font-variant-ligatures: normal; font-variant-caps: normal;
font-weight: 400; letter-spacing: normal; text-align: left;
text-indent: 0px; text-transform: none; white-space: normal;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255); text-decoration-style:
initial; text-decoration-color: initial; display: inline
!important; float: none;"><span style="color: rgb(36, 41, 46);
font-size: 16px; font-style: normal; font-variant-ligatures:
normal; font-variant-caps: normal; font-weight: 400;
letter-spacing: normal; text-align: left; text-indent: 0px;
text-transform: none; white-space: normal; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(255, 255,
255); text-decoration-style: initial; text-decoration-color:
initial; display: inline !important; float: none;">retention
purge now</span>, previously they were aggressively deleted.<br>
* Previously timeout for WAL streaming was always equal to zero,
now its value depends on "--archive-timeout" parameter.<br>
* Previously using the "--recovery-target-lsn" option with
"validate" command was leading to validation of all backups
instead of PITR validation.<br>
* Now only valid backups can be choosen for PITR and validation of
PITR if backup ID is not specified.<br>
<br>
</span>New features:<br>
* WAL archive catalog. Now it is possible to view the state of every
WAL timeline in archive.<br>
* Backup Pinning. Now it is possible to exclude a backup from
established retention policy or, in other words, "pin" it for a
specified amount of time.<br>
* WAL archive retention. Now it is possible to set the "depth" of
WAL stored in archive measured in backups per timeline.<br>
* Partial restore. Now it is possible to restore only the specified
databases or exclude the specified databases from restore.<br>
<br>
For more details can be found in the release notes:<br>
<a
href="https://github.com/postgrespro/pg_probackup/releases/tag/2.2.1">https://github.com/postgrespro/pg_probackup/releases/tag/2.2.1</a><br>
<p><br>
Download
<br>
--------
<br>
<a class="moz-txt-link-freetext"
href="https://github.com/postgrespro/pg_probackup">https://github.com/postgrespro/pg_probackup</a></p>
<pre class="moz-signature" cols="72">--
Grigory Smolkin
Postgres Professional: <a class="moz-txt-link-freetext" href="http://www.postgrespro.com">http://www.postgrespro.com</a>
The Russian Postgres Company</pre>
</body>
</html>
--------------543EDB2C8470E2691517F12E--