From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Purpose of pg_dump tar archive format? |
Date: | 2024-06-04 15:33:47 |
Message-ID: | 7005ac8c-2f83-4122-9172-04bca268f987@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 6/4/24 08:25, Ron Johnson wrote:
> On Tue, Jun 4, 2024 at 10:43 AM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com
> <mailto:adrian(dot)klaver(at)aklaver(dot)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(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2024-06-04 16:53:58 | Re: Purpose of pg_dump tar archive format? |
Previous Message | Ron Johnson | 2024-06-04 15:25:05 | Re: Purpose of pg_dump tar archive format? |