Re: Custom format for pg_dumpall

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Philip Warner <pjw(at)rhyme(dot)com(dot)au>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, 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-16 00:12:00
Message-ID: 8954.1079395920@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Philip Warner <pjw(at)rhyme(dot)com(dot)au> writes:
>> I'm envisioning
>> some super-archive format in which there are individual entries
>> containing the pg_dump output for each database

> Not sure about this. I'd be inclined to investigate just adding another
> attribute to each TOC entry (database_name).

That seems like it would complicate both pg_dump and pg_restore unduly.
I'd rather keep both of them as simple one-database programs. To take
just one objection, people are accustomed to be able to load a pg_dump
from database foo into a database with a different name; that would be
either impossible or very klugy if we do what you're thinking of.

>> This does seem like a nice solution to the perennial problem of dumping
>> blobs easily.

> What is this?

That you can't use pg_dumpall if you want to dump blobs too.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joshua D. Drake 2004-03-16 00:14:05 Re: Log rotation
Previous Message Philip Warner 2004-03-16 00:04:30 Re: Custom format for pg_dumpall