Re: tar-related code in PostgreSQL

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: tar-related code in PostgreSQL
Date: 2020-04-27 18:07:47
Message-ID: CA+TgmoaxG17TzEX0VTpY3Uaps3YGoegyCgv8U02-Fp-T5dY1AQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Apr 24, 2020 at 12:27 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Darafei Komяpa Praliaskouski 2020-04-27 18:48:47 Re: Parallel GiST build on Cube
Previous Message Peter Geoghegan 2020-04-27 18:02:59 Fixes for two separate bugs in nbtree VACUUM's page deletion