| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Mark Woodward <pgsql(at)mohawksoft(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Multiple logical databases |
| Date: | 2006-02-02 15:13:30 |
| Message-ID: | 1138893210.3105.7.camel@swithin |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
On Thu, 2006-02-02 at 10:23 -0500, Mark Woodward wrote:
> If one db is REALLY REALLY huge and doesn't change, and a few
> others are small and change often, pg_dumpall will spend most of its time
> dumping the unchanging data.
>
My usual backup strategy does pg_dumpall -g to get the (tiny) global
data, and then pg_dump for each individual database. Quite apart from
anything else I prefer to have custom format dumps anyway, but I think
this should meet your need for less frequent dumping of some constant
database.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-02-02 15:19:04 | Re: Multiple logical databases |
| Previous Message | Kim Bisgaard | 2006-02-02 14:35:50 | Re: Question about ALTER TABLE SET TABLESPACE locing |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-02-02 15:19:04 | Re: Multiple logical databases |
| Previous Message | Joachim Wieland | 2006-02-02 09:00:15 | TODO-Item: TRUNCATE ... CASCADE |