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

Поиск
Список
Период
Сортировка
От Tomas Szepe
Тема 8.3.0: vacuum full analyze: "invalid memory alloc request size"
Дата
Msg-id 20080209115221.GA27757@louise.pinerecords.com
обсуждение исходный текст
Ответы Re: 8.3.0: vacuum full analyze: "invalid memory alloc request size"  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-bugs
Hello,

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

But not always, sometimes it goes through w/o a problem:

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
WARNING:  skipping "pg_tablespace" --- only table or database owner can vacuum it
WARNING:  skipping "pg_pltemplate" --- only table or database owner can vacuum it
VACUUM

This is on x86 Linux.  8.2.6 does not exhibit the problem, or at least I haven't
run into it.  What info do I need to submit so that this can be tracked down?

Best regards,
--
Tomas Szepe <szepe@pinerecords.com>

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

Предыдущее
От: "Holger Klawitter"
Дата:
Сообщение: BUG #3945: unexpected ON INSERT rule behaviour
Следующее
От: Tom Lane
Дата:
Сообщение: Re: 8.3.0: vacuum full analyze: "invalid memory alloc request size"