Re: Non-text mode for pg_dumpall - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: Non-text mode for pg_dumpall
Date
Msg-id CABUevEwv4kQ5of9e+3mZ=Q9ZfkNtDbidPCLuDU_sm00d2Yf-rQ@mail.gmail.com
Whole thread Raw
In response to Re: Non-text mode for pg_dumpall  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Mon, Jun 10, 2024 at 6:21 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
Magnus Hagander <magnus@hagander.net> writes:
> On Mon, Jun 10, 2024 at 5:03 PM Nathan Bossart <nathandbossart@gmail.com>
> wrote:
>> Is there a particular advantage to that approach as opposed to just using
>> "directory" mode for everything?

> A gazillion files to deal with? Much easier to work with individual custom
> files if you're moving databases around and things like that.
> Much easier to monitor eg sizes/dates if you're using it for backups.

You can always tar up the directory tree after-the-fact if you want
one file.  Sure, that step's not parallelized, but I think we'd need
some non-parallelized copying to create such a file anyway.

That would require double the disk space.

But you can also just run pg_dump manually on each database and a pg_dumpall -g like people are doing today -- I thought this whole thing was about making it more convenient :)
 
--

pgsql-hackers by date:

Previous
From: Mark Hill
Date:
Subject: ODBC Source Downloads Missing
Next
From: Andres Freund
Date:
Subject: Re: Proposal: Document ABI Compatibility