| From: | Tomasz Myrta <jasiek(at)klaster(dot)net> |
|---|---|
| To: | Rudi Starcevic <rudi(at)oasis(dot)net(dot)au> |
| Cc: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: pg_dump problem |
| Date: | 2003-01-01 11:34:49 |
| Message-ID: | 3E12D259.8020300@klaster.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
Rudi Starcevic wrote:
>Hi,
>
>After doing a pg_dump on a database I'm unable to access the file.
>
>My command is simply 'mv' ::
>
>mv camper.dump20020116 camper_bak/
>
>The error I get is ::
>
>mv: camper.dump20020116: Value too large for defined data type
>
>Strange. It seems to be saying the file I created is too large to handle.
>Do you know where I've gone wrong ?
>I just want to dump one of my databases, move it to a back up dir. then
>make changes to the running database.
It looks like you have not a postgres, but filesystem problem. How big is this file?
Anyway pg_dump can save filedump in gzip format, which is better for further backuping.
Regards,
Tomasz Myrta
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomasz Myrta | 2003-01-01 12:41:43 | Re: Implementing automatic updating of primary keys... |
| Previous Message | Jie Liang | 2002-12-31 19:09:33 | Re: plpgsql select into question |