From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Non-text mode for pg_dumpall |
Date: | 2024-06-10 14:14:08 |
Message-ID: | ZmcKMF61K4Ck51dK@nathan |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jun 10, 2024 at 08:58:49AM -0400, Andrew Dunstan wrote:
> Tom and Nathan opined recently that providing for non-text mode for
> pg_dumpall would be a Good Thing (TM). Not having it has been a
> long-standing complaint, so I've decided to give it a go.
Thank you!
> I think we would need to restrict it to directory mode, at least to begin
> with. I would have a toc.dat with a different magic block (say "PGGLO"
> instead of "PGDMP") containing the global entries (roles, tablespaces,
> databases). Then for each database there would be a subdirectory (named for
> its toc entry) with a standard directory mode dump for that database. These
> could be generated in parallel (possibly by pg_dumpall calling pg_dump for
> each database). pg_restore on detecting a global type toc.data would restore
> the globals and then each of the databases (again possibly in parallel).
I'm curious why we couldn't also support the "custom" format.
> Following that I would turn my attention to using it in pg_upgrade.
+1
--
nathan
From | Date | Subject | |
---|---|---|---|
Next Message | Dean Rasheed | 2024-06-10 14:21:35 | Re: Proposal to include --exclude-extension Flag in pg_dump |
Previous Message | cca5507 | 2024-06-10 14:04:31 | Re: Historic snapshot doesn't track txns committed in BUILDING_SNAPSHOT state |