Re: Purpose of pg_dump tar archive format?
Erik Wienhold <ewie@ewie.name>
From: Erik Wienhold <ewie@ewie.name>
To: Ron Johnson <ronljohnsonjr@gmail.com>
Cc: pgsql-general <pgsql-general@postgresql.org>
Date: 2024-06-04T13:48:50Z
Lists: pgsql-general
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
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Add 'directory' format to pg_dump. The new directory format is compatible
- 7f508f1c6b51 9.1.0 cited