Re: pg_dump large-file support > 16GB - Mailing list pgsql-general

From Rafael Martinez
Subject Re: pg_dump large-file support > 16GB
Date
Msg-id 1111134756.30774.9.camel@linux.site
Whole thread Raw
In response to Re: pg_dump large-file support > 16GB  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pg_dump large-file support > 16GB
List pgsql-general
On Thu, 2005-03-17 at 10:17 -0500, Tom Lane wrote:
> Rafael Martinez Guerrero <r.m.guerrero@usit.uio.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

- In this example, it is a plain text (--format=p).
- If I write to stdout and redirect to a file, the dump finnish without
problems and I get a dump-text-file over 16GB without problems.


--
Rafael Martinez, <r.m.guerrero@usit.uio.no>
Center for Information Technology Services
University of Oslo, Norway

PGP Public Key: http://folk.uio.no/rafael/

Attachment

pgsql-general by date:

Previous
From: Michael Fuhr
Date:
Subject: Re: plpython function problem workaround
Next
From: Rafael Martinez
Date:
Subject: Re: pg_dump large-file support > 16GB