From: | "Cyril VELTER" <cyril(dot)velter(at)metadys(dot)com> |
---|---|
To: | dev(at)archonet(dot)com |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | [Re] Re: [Re] Re: Unknown winsock error 10061while dumping a big database |
Date: | 2007-11-28 13:03:18 |
Message-ID: | 0-39414523071-2674-2275834@CFGEM |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
De : mailto:dev(at)archonet(dot)com
> Cyril VELTER wrote:
> >
> > maintenance_work_mem and work_mem are set to their default value (16M /
1M).
> > Does Copy use any of these values ? The doc only state sort operations for
> > work_mem and vacuum / create index / alter table add foreing key for
> > maintenance_work_mem.
>
> You'll probably want to increase both of those (assuming you have a few
> gigs of RAM).
The server have 4G of ram. But doing a search in the source code it does not
seem that these values are used during a copy operation. I will try to increase
these values.
>
> > BTW, just dumping this table fail with the same error.
>
> Hmm - what version of 8.2 are you running on Windows?
>
> It's just that 8.2.4 has a fix that says:
>
> Allow pg_dump to do binary backups larger than two gigabytes on Windows
> (Magnus)
>
> Now, whether that will affect you I'm not sure, since you said you were
> dumping from Linux, with the server on Windows.
I don't think so. The dump stop at 75GB (the 2GB limit is not a problem), I'm
running 8.2.5 on both the client and the server and the dump is done on a linux
machine.
Cyril VELTER
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Huxton | 2007-11-28 13:16:52 | Re: [Re] Re: [Re] Re: Unknown winsock error 10061while dumping a big database |
Previous Message | Simon Riggs | 2007-11-28 13:00:35 | Re: WAL Recovery |