| From: | Shaheed Haque <shaheedhaque(at)gmail(dot)com> |
|---|---|
| To: | Gavin Roy <gavinr(at)aweber(dot)com> |
| Cc: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Purpose of pg_dump tar archive format? |
| Date: | 2024-06-04 21:35:21 |
| Message-ID: | CAHAc2jeAiUzTv=MFY3EGgWF5LPJ6k-nOa0-_xekyDamnLehFNg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, 4 Jun 2024 at 20:47, Gavin Roy <gavinr(at)aweber(dot)com> wrote:
>
> On Tue, Jun 4, 2024 at 3:15 PM Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
> wrote:
>
>>
>> But why tar instead of custom? That was part of my original question.
>>
>
> I've found it pretty useful for programmatically accessing data in a dump
> for large databases outside of the normal pg_dump/pg_restore workflow. You
> don't have to seek through one large binary file to get to the data section
> to get at the data.
>
This is true for us too; specifically, tar, including with compression, is
very convenient for both CLI and Python ecosystems.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Koen De Groote | 2024-06-04 22:55:42 | Questions on logical replication |
| Previous Message | Tom Lane | 2024-06-04 20:31:34 | Re: Unexpected results from CALL and AUTOCOMMIT=off |