| From: | Marco Colombo <pgsql(at)esiway(dot)net> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: pg_dump large-file support > 16GB |
| Date: | 2005-03-17 14:57:44 |
| Message-ID: | Pine.LNX.4.61.0503171553311.20758@Megathlon.ESI |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, 17 Mar 2005, Rafael Martinez Guerrero wrote:
> My question is why is this limit (16GB) there, when my OS does not have
> that limit? Is it possible to take it away in a easy way? It looks like
> pg_dump is compiled with large-file support because it can work with
> files bigger than 4GB.
>
> More ideas? :)
Things to try:
a) shell redirection:
$ pg_dump ... > outfile
b) some pipes:
$ pg_dump ... | cat > outfile
$ pg_dump ... | dd of=outfile
a) may fail if there's something with pg_dump and large files.
b) is different in that it's the right side of the pipe that outputs
to the filesystem.
.TM.
--
____/ ____/ /
/ / / Marco Colombo
___/ ___ / / Technical Manager
/ / / ESI s.r.l.
_____/ _____/ _/ Colombo(at)ESI(dot)it
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martijn van Oosterhout | 2005-03-17 15:04:51 | Re: plpython function problem workaround |
| Previous Message | Scott Marlowe | 2005-03-17 14:51:13 | Re: rserv question |