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

From Nathan Bossart
Subject Re: Non-text mode for pg_dumpall
Date
Msg-id ZmcnwlQ0arj532zF@nathan
Whole thread Raw
In response to Re: Non-text mode for pg_dumpall  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
On Mon, Jun 10, 2024 at 05:45:19PM +0200, Magnus Hagander wrote:
> 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?  I know pg_upgrade uses "custom" mode for
>> each of the databases, so a combo approach would be a closer match to the
>> existing behavior, but that doesn't strike me as an especially strong
>> reason to keep doing it that way.
> 
> 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.
> 
> It's not things that are make-it-or-break-it or anything, but there are
> some smaller things that definitely can be useful.

Makes sense, thanks for elaborating.

-- 
nathan



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: list_free in addRangeTableEntryForJoin
Next
From: Tom Lane
Date:
Subject: Re: Non-text mode for pg_dumpall