Re: Purpose of pg_dump tar archive format?
Adrian Klaver <adrian.klaver@aklaver.com>
From: Adrian Klaver <adrian.klaver@aklaver.com>
To: Ron Johnson <ronljohnsonjr@gmail.com>,
pgsql-general <pgsql-general@postgresql.org>
Date: 2024-06-04T15:33:47Z
Lists: pgsql-general
On 6/4/24 08:25, Ron Johnson wrote: > On Tue, Jun 4, 2024 at 10:43 AM Adrian Klaver <adrian.klaver@aklaver.com > <mailto:adrian.klaver@aklaver.com>> wrote: > > On 6/4/24 05:13, 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). > > pg_dump -d test -U postgres -Ft | gzip --stdout > test.tgz > > > Who's got meaningful databases that small anymore? > > And if you've got meaningfully sized databases, open port 5432 and move > them using pg_dump. If you don't need the tar format then don't use it. -- Adrian Klaver adrian.klaver@aklaver.com
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