Re: pg_dumpall 8.1.4 large objects error

Поиск
Список
Период
Сортировка
От Jeff Frost
Тема Re: pg_dumpall 8.1.4 large objects error
Дата
Msg-id Pine.LNX.4.64.0606090926420.27250@glacier.frostconsultingllc.com
обсуждение исходный текст
Ответ на Re: pg_dumpall 8.1.4 large objects error  (Jeff Frost <jeff@frostconsultingllc.com>)
Список pgsql-admin
On Fri, 9 Jun 2006, Jeff Frost wrote:

> Got the REINDEX completed and found a new error that I haven't seen before:
>
> pg_dump: SQL command failed
> pg_dump: Error message from server: ERROR:  Memory exhausted in
> AllocSetAlloc(96)
> pg_dump: The command was: FETCH 100 IN blobcmt
> pg_dumpall: pg_dump failed on database "vsl_cs", exiting
>
> I was dumping like so:
>
> /usr/local/pgsql-8.1.4/bin/pg_dumpall | /usr/bin/bzip2 >
> vsl_cs-20060608.sql.bz2
>
> Would it be better and more efficient to just pg_dumpall the globals and
> pg_dump in custom format the vsl_cs db?  There's actually only one DB on the
> systems besides the system dbs.  Server is 7.3.2, and the plan is to upgrade
> it.

Hit send before i was done:

ulimit -d shows:

bash-2.05b$ ulimit -d
unlimited

The free output on the system looks like this:

bash-2.05b$ free
              total       used       free     shared    buffers     cached
Mem:       1031024     481548     549476          0      30620     359524
-/+ buffers/cache:      91404     939620
Swap:      2562328     193992    2368336



--
Jeff Frost, Owner     <jeff@frostconsultingllc.com>
Frost Consulting, LLC     http://www.frostconsultingllc.com/
Phone: 650-780-7908    FAX: 650-649-1954

В списке pgsql-admin по дате отправления:

Предыдущее
От: "Joshua D. Drake"
Дата:
Сообщение: Re: Best way to index large text/varchar fields
Следующее
От: Tom Lane
Дата:
Сообщение: Re: pg_dumpall 8.1.4 large objects error