| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Custom format for pg_dumpall |
| Date: | 2004-03-15 15:00:54 |
| Message-ID: | 22988.1079362854@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Christopher Kings-Lynne wrote:
>> Why is there no custom format dump option for pg_dumpall?
> I think it is because we have no mechanism to merge multiple custom
> format files from different databases into a single file. Perhaps this
> is a TODO.
It would probably require changes in pg_dump to append custom-format
output to an existing file, but offhand I see no fundamental obstacle
now that pg_dumpall is a C program. (I think it would've been real
painful to construct an archive from a shell script...) I'm envisioning
some super-archive format in which there are individual entries
containing the pg_dump output for each database, plus an entry for the
"global" users-and-groups info.
This does seem like a nice solution to the perennial problem of dumping
blobs easily.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2004-03-15 15:58:21 | Re: remove log_timestamp, log_pid and log_source_port GUC |
| Previous Message | Tom Lane | 2004-03-15 14:39:37 | Re: Further thoughts about warning for costly FK checks |