Re: 8.3.0: vacuum full analyze: "invalid memory alloc request size"

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: 8.3.0: vacuum full analyze: "invalid memory alloc request size"
Дата
Msg-id 24857.1202577567@sss.pgh.pa.us
обсуждение исходный текст
Ответ на 8.3.0: vacuum full analyze: "invalid memory alloc request size"  (Tomas Szepe <szepe@pinerecords.com>)
Ответы Re: 8.3.0: vacuum full analyze: "invalid memory alloc request size"  (Tomas Szepe <szepe@pinerecords.com>)
Список pgsql-bugs
Tomas Szepe <szepe@pinerecords.com> writes:
> Trying to run "vacuum full analyze" on a ~200MB UTF8 database fails with:

> fs=> vacuum full analyze;
> WARNING:  skipping "pg_authid" --- only table or database owner can vacuum it
> WARNING:  skipping "pg_database" --- only table or database owner can vacuum it
> WARNING:  skipping "pg_shdepend" --- only table or database owner can vacuum it
> WARNING:  skipping "pg_shdescription" --- only table or database owner can vacuum it
> WARNING:  skipping "pg_auth_members" --- only table or database owner can vacuum it
> ERROR:  invalid memory alloc request size 4294965504

Hmm, please see if you can get a stack trace from that (set the
breakpoint at errfinish()).  You might want to use vacuum verbose
first so that you can figure out which individual table is causing it.

            regards, tom lane

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

Предыдущее
От: Tomas Szepe
Дата:
Сообщение: 8.3.0: vacuum full analyze: "invalid memory alloc request size"
Следующее
От: "Lee Ottaway"
Дата:
Сообщение: BUG #3947: Unable to Initialize Data Cluster