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-06-15 20:49:04
Message-ID: CA+Tgmobx3GxWvfeHTyjTSMj=hoQQcdXK3i1qw6QR3Kr57+ePeA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Apr 27, 2020 at 2:07 PM Robert Haas <robertmhaas(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2020-06-15 21:09:05 Re: Parallel Seq Scan vs kernel read ahead
Previous Message Surafel Temesgen 2020-06-15 20:26:13 pg_dump --where option