8 Mar 2006 07:31:19 -0800, Nik <[EMAIL PROTECTED]>:
> [...]
> psql: ERROR: out of memory
> DETAIL: Failed on request of size 32.
>
I also have this kind of error (out of memory) during the restoration
of objects on my database. I use a 8.1.2 pg_dump on a 7.1.1 PostgreSQL
server. Size of the dump i
Yes, I was indeed out of memory. That is the problem: the postgres.exe
process corresponding to the pg_restore continuously consumes more and
more memory until it runs out and fails with the mentioned error. Since
I already have 4Gb of RAM, throwing more hardware at it is not a
feasible solution, s
Tom was exactly right.
I was trying to restore the dump file into an already created table
structure that did have three foreign key constraints. I removed the
primary key constraint to speed up the load, but was not aware of the
memory usage of the foreign keys.
I dropped the table and ran the p
other way is to set
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session
Manager\Memory Management
bigger values
but to restore a lot of data on windows take so many time
2006/3/8, Tom Lane <[EMAIL PROTECTED]>:
> "Nik" <[EMAIL PROTECTED]> writes:
> > pg_restore: ERROR: out of memory
> > D
"Nik" <[EMAIL PROTECTED]> writes:
> pg_restore: ERROR: out of memory
> DETAIL: Failed on request of size 32.
> CONTEXT: COPY lane_data, line 17345022: ""
A COPY command by itself shouldn't eat memory. I'm wondering if the
table being copied into has any AFTER triggers on it (eg for foreign key
Nik wrote:
I am running PostgreSQL 8.1.3 on Windows 2003 Server.
I am trying to transfer the data from a table in db1on one machine to a
table in db2 on a different machine. The table size is about 22Gb
(about 280 million rows).
I was trying to do it by generating a backup file of the table in
