Re: Deprecating, and scheduling removal of, pg_dump's tar format.

From: Christophe Pettus <xof(at)thebuild(dot)com>
To: Peter Geoghegan <pg(at)bowt(dot)ie>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
Subject: Re: Deprecating, and scheduling removal of, pg_dump's tar format.
Date: 2018-07-27 02:41:39
Message-ID: 4E9BC39D-6416-4766-8680-644A1A991F8B@thebuild.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> On Jul 26, 2018, at 19:35, Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
>
> Why, specifically, would it make them unhappy?

Forensic and archive backups in .tar format (which I know of users doing) would require a two-step restore process on newer versions.

--
-- Christophe Pettus
xof(at)thebuild(dot)com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2018-07-27 02:42:45 Re: negative bitmapset member not allowed Error with partition pruning
Previous Message Andres Freund 2018-07-27 02:38:46 Re: Deprecating, and scheduling removal of, pg_dump's tar format.