| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Trond Eivind Glomsrød <teg(at)redhat(dot)com> |
| Cc: | Efrain Caro <betsemes(at)hotmail(dot)com>, Jeff Hoffmann <jeff(at)propertykey(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Redhat 7 and PgSQL |
| Date: | 2000-09-29 17:03:52 |
| Message-ID: | Pine.LNX.4.21.0009291859330.363-100000@peter |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Trond Eivind Glomsrød writes:
> Incidentally, you can dump data from a database. You can also insert
> data into a database. If you do this before and after upgrading,
> you'll hopefully have the same data in the database.
If there's a problem with pg_dump then pg_dump needs to be fixed, and
incidentally, Philip Warner has been doing just that.
But claiming that you can't upgrade is painting over what might rather be
a deficiency in the RPM mechanism, ISTM. Why can't you have a spec file
like this:
%preupgrade
pg_dumpall >somewhere
%postupgrade
...
psql -f somewhere
--
Peter Eisentraut peter_e(at)gmx(dot)net http://yi.org/peter-e/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Trond Eivind =?iso-8859-1?q?Glomsr=F8d?= | 2000-09-29 17:04:24 | Re: Redhat 7 and PgSQL |
| Previous Message | Ross J. Reedstrom | 2000-09-29 16:57:11 | Re: pg_dump's over 2GB |