Horton

Re: tar-related code in PostgreSQL

Robert Haas <robertmhaas@gmail.com>

View thread View on postgr.es
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-04-27T18:07:47Z
Lists: pgsql-hackers 
On Fri, Apr 24, 2020 at 12:27 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Bleah.  Whether or not the nearest copy of tar happens to spit up on
> that, it's a clear violation of the POSIX standard for tar files.
> I'd vote for back-patching your 0001.

Done.

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

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Commits

  1. Assorted cleanup of tar-related code.

  2. Fix bogus tar-file padding logic for standby.signal.

  3. Integrate recovery.conf into postgresql.conf