Re: tar-related code in PostgreSQL
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Hamid Akhtar <hamid.akhtar@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2020-06-29T11:52:46Z
Lists: pgsql-hackers
On Sun, Jun 28, 2020 at 11:24 AM Hamid Akhtar <hamid.akhtar@gmail.com> wrote: > The following review has been posted through the commitfest application: > make installcheck-world: tested, passed > Implements feature: tested, passed > Spec compliant: not tested > Documentation: not tested > > The patch works perfectly. > > The new status of this patch is: Ready for Committer Thanks, but this was committed on June 15th, as per my previous email. Perhaps I forgot to update the CommitFest application.... -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Commits
-
Assorted cleanup of tar-related code.
- 2961c9711c17 14.0 landed
-
Fix bogus tar-file padding logic for standby.signal.
- a08bfe742492 12.3 landed
- 0278d3f79a30 13.0 landed
-
Integrate recovery.conf into postgresql.conf
- 2dedf4d9a899 12.0 cited