Date: Tue, 4 Jun 2024 15:48:50 +0200
From: Erik Wienhold <ewie@ewie.name>
To: Ron Johnson <ronljohnsonjr@gmail.com>
Cc: pgsql-general <pgsql-general@postgresql.org>
Subject: Re: Purpose of pg_dump tar archive format?
Message-ID: <d7a726fb-2b9b-4b18-885d-1b7452ccd867@ewie.name>
References: <CANzqJaAHOSNiOhe4D2hOBB46=puWQOZb=s=VQdNmUSOtOmRG5A@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CANzqJaAHOSNiOhe4D2hOBB46=puWQOZb=s=VQdNmUSOtOmRG5A@mail.gmail.com>
Archived-At: <https://www.postgresql.org/message-id/d7a726fb-2b9b-4b18-885d-1b7452ccd867%40ewie.name>
Precedence: bulk

On 2024-06-04 14:13 +0200, Ron Johnson wrote:
> It doesn't support compression nor restore reordering like the custom
> format, so I'm having trouble seeing why it still exists (at least without
> a doc warning that it's obsolete).

Maybe because of this:

> *	The tar format also includes a 'restore.sql' script which is there for
> *	the benefit of humans. This script is never used by pg_restore.

I've never used that restore.sql, so I can't say how useful it is,
especially since it requires editing $$PATH$$.  Should be mentioned in
the docs if that file is still relevant.

-- 
Erik