Re: Re: HOLD THE PRESSES!! ... pg_dump from v7.0.3 can't import to v7.1?

From: darcy(at)druid(dot)net (D'Arcy J(dot)M(dot) Cain)
To: The Hermit Hacker <scrappy(at)hub(dot)org>
Cc: Joel Burton <jburton(at)scw(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Re: HOLD THE PRESSES!! ... pg_dump from v7.0.3 can't import to v7.1?
Date: 2001-04-11 10:27:18
Message-ID: 20010411102718.4A4FE1A7D@druid.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thus spake The Hermit Hacker
> all 77 databases got dump'd as the same database:

Personally I never use pg_dumpall. It is easy to write a script to get
the list of databases and use pg_dump to dump them individually. In fact
I like dumping individual tables if I can. Mostly I like the ability to
fix one table if there is a problem. Finding and fixing one 7 row table
in a multi-gigabyte files really sucks. :-)

--
D'Arcy J.M. Cain <darcy(at){druid|vex}.net> | Democracy is three wolves
http://www.druid.net/darcy/ | and a sheep voting on
+1 416 425 1212 (DoD#0082) (eNTP) | what's for dinner.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Philip Warner 2001-04-11 11:40:41 Re: Re: HOLD THE PRESSES!! ... pg_dump from v7.0.3 can't import to v7.1?
Previous Message Marcin Wasilewski 2001-04-11 09:56:13 Languages