From: | Aly Dharshi <aly(dot)dharshi(at)telus(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Rafael Martinez Guerrero <r(dot)m(dot)guerrero(at)usit(dot)uio(dot)no>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: pg_dump large-file support > 16GB |
Date: | 2005-03-17 17:41:34 |
Message-ID: | 4239C14E.90101@telus.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Would it help to use a different filesystem like SGI's XFS ? Would it be
possible to even implement that at you site at this stage ?
Tom Lane wrote:
> Rafael Martinez Guerrero <r(dot)m(dot)guerrero(at)usit(dot)uio(dot)no> writes:
>
>>We are trying to dump a 30GB+ database using pg_dump with the --file
>>option. In the beginning everything works fine, pg_dump runs and we get
>>a dumpfile. But when this file becomes 16GB it disappears from the
>>filesystem, pg_dump continues working without giving an error until it
>>finnish (even when the file does not exist)(The filesystem has free
>>space).
>
>
> Is that a plain text, tar, or custom dump (-Ft or -Fc)? Is the behavior
> different if you just write to stdout instead of using --file?
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org
--
Aly Dharshi
aly(dot)dharshi(at)telus(dot)net
"A good speech is like a good dress
that's short enough to be interesting
and long enough to cover the subject"
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Fuhr | 2005-03-17 17:51:28 | Re: GUID data type support |
Previous Message | Michal Hlavac | 2005-03-17 16:53:52 | GUID data type support |