Re: Out of memory error on pg_restore
От | Moises Alberto Lindo Gutarra |
---|---|
Тема | Re: Out of memory error on pg_restore |
Дата | |
Msg-id | 5db591c00603081310s339e7f0bh@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Out of memory error on pg_restore (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Out of memory error on pg_restore
|
Список | pgsql-general |
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 <tgl@sss.pgh.pa.us>: > "Nik" <XLPizza@gmail.com> writes: > > pg_restore: ERROR: out of memory > > DETAIL: Failed on request of size 32. > > CONTEXT: COPY lane_data, line 17345022: "<line of data goes here>" > > 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 > checks), as each pending trigger event uses memory and so a copy of a > lot of rows could run out. > > pg_dump scripts ordinarily load data before creating triggers or foreign > keys in order to avoid this problem. Perhaps you were trying a > data-only restore? If so, best answer is "don't do that". A plain > combined schema+data dump should work. > > regards, tom lane > > ---------------------------(end of broadcast)--------------------------- > TIP 2: Don't 'kill -9' the postmaster >
В списке pgsql-general по дате отправления: