Re: tar-related code in PostgreSQL

Robert Haas <robertmhaas@gmail.com>

From: Robert Haas <robertmhaas@gmail.com>

To: Tom Lane <tgl@sss.pgh.pa.us>

Cc: "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>

Date: 2020-06-15T20:49:04Z

Lists: pgsql-hackers

On Mon, Apr 27, 2020 at 2:07 PM Robert Haas <robertmhaas@gmail.com> wrote:
> > I'd lean mildly to holding 0002 until after we branch.  It probably
> > won't break anything, but it probably won't fix anything either.
>
> True.

Committed now.

-- 
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