Re: [GENERAL] Encoding problem using pg_dumpall - Mailing list pgsql-admin

From Michael Monnerie
Subject Re: [GENERAL] Encoding problem using pg_dumpall
Date
Msg-id 200901301223.49703@zmi.at
Whole thread Raw
In response to Re: [GENERAL] Encoding problem using pg_dumpall  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [GENERAL] Encoding problem using pg_dumpall  (Cliff Pratt <enkiduonthenet@gmail.com>)
List pgsql-admin
On Freitag 30 Januar 2009 Tom Lane wrote:
> The -Fc (and -Ft) formats are only designed to hold the contents of a
> single database; and pg_restore only knows how to restore into a
> single database.
>
> If you feel like fixing that, step right up.

Sorry, didn't want to step on toes here. I know that sometimes if you
perfectly know a system you get blind over alternatives, and wanted to
throw in an idea.

The format of pg_dumpall could be a tar of single pg_dumps as well,
making pg_dumpall just call pg_dump for each db, putting that output
into the tar output from pg_dumpall. But again, just an idea, I don't
mind really. I'm just a sysadmin who wants things as easy as possible.
Maybe fixing pg_dumpall to include that -E is easier.

mfg zmi
--
// Michael Monnerie, Ing.BSc    -----      http://it-management.at
// Tel: 0660 / 415 65 31                      .network.your.ideas.
// PGP Key:         "curl -s http://zmi.at/zmi.asc | gpg --import"
// Fingerprint: AC19 F9D5 36ED CD8A EF38  500E CE14 91F7 1C12 09B4
// Keyserver: wwwkeys.eu.pgp.net                  Key-ID: 1C1209B4


pgsql-admin by date:

Previous
From: Jaume Sabater
Date:
Subject: Re: Warm standby recovery failure
Next
From: Suresh Borse
Date:
Subject: How to migrate from oracle to postgres !!