From: | "James Kelty" <jamesk(at)ashlandagency(dot)com> |
---|---|
To: | "PgSQL Novice ML" <pgsql-novice(at)postgresql(dot)org> |
Subject: | Re: File size limit on pg_dumpall |
Date: | 2002-08-06 20:39:30 |
Message-ID: | LIEBJHJEFMPDEOMFHCAOCENBCIAA.jamesk@ashlandagency.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Hmmm. Well, thanks for that. I, luckily, am not working on a needed system,
so I am just gonna re-install the data with our custom loader. Thanks,
though!
-James
-----Original Message-----
From: pgsql-novice-owner(at)postgresql(dot)org
[mailto:pgsql-novice-owner(at)postgresql(dot)org]On Behalf Of Ron Johnson
Sent: Tuesday, August 06, 2002 1:44 PM
To: PgSQL Novice ML
Subject: Re: [NOVICE] File size limit on pg_dumpall
On Tue, 2002-08-06 at 15:00, James Kelty wrote:
> Hello.
>
> I am upgrading from 7.1.3 to 7.2.1 (yeah!), but I ran into a problem
(boo!).
> I did a pg_dumpall on the database before I upgraded, per the
instructions.
> But, the file was something like 5.5G. So, of course, psql -f filename
> complains that it is too large. Any work around?
COPY out some big tables, then drop them. Then, the pg_dumpall output
won't be so big. Of course, you'd then have to COPY in the files and
re-index them...
--
+-----------------------------------------------------------------+
| Ron Johnson, Jr. Home: ron(dot)l(dot)johnson(at)cox(dot)net |
| Jefferson, LA USA |
| |
| "The greatest dangers to liberty lurk in insidious encroachment |
| by men of zeal, well-meaning, but without understanding." |
| Justice Louis Brandeis, dissenting, Olmstead v US (1928) |
+-----------------------------------------------------------------+
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster
From | Date | Subject | |
---|---|---|---|
Next Message | Ron Johnson | 2002-08-06 20:43:57 | Re: File size limit on pg_dumpall |
Previous Message | James Kelty | 2002-08-06 20:00:04 | File size limit on pg_dumpall |