Re: Restoring a pg_dump fails with
От | Reiner Dassing |
---|---|
Тема | Re: Restoring a pg_dump fails with |
Дата | |
Msg-id | 3AF018A5.2F424492@wettzell.ifag.de обсуждение исходный текст |
Ответ на | Restoring a pg_dump fails with (Reiner Dassing <dassing@wettzell.ifag.de>) |
Ответы |
Re: Restoring a pg_dump fails with
|
Список | pgsql-admin |
Hello Tom! I would like to contact you again with two phenomenas which are important in my opinion: 1. The error "Memory exhausted in AllocSetAlloc(32)" is there on the "delete from table" command, also. 2. There are some warnings during compilation which seems to be strange. to 1.: The following protocol will show the effect of "Memory exhausted": sh-2.04$ psql wetter Welcome to psql, the PostgreSQL interactive terminal. Type: \copyright for distribution terms \h for help with SQL commands \? for help on internal slash commands \g or terminate with semicolon to execute query \q to quit wetter=# vacuum analyze wetter; VACUUM wetter=# delete from wetter; ERROR: Memory exhausted in AllocSetAlloc(32) <----------- !!!!!!!!! wetter=# select count(*) from wetter; count --------- 4457236 (1 row) wetter=# \quit To 2: During compilation there are the following warnings: cc -std -O4 -Olimit 2000 -I../../../../src/include -c -o regproc.o regproc.c cc: Info: regproc.c, line 140: In this statement, an array subscript expression is either less than zero or greater than the largest value that can be represented by the size_t type. (badsubscript) result = (RegProcedure) heap_getattr(proctup, cc -std -O4 -Olimit 2000 -I../../../../src/include -c -o inval.o inval.c cc: Info: inval.c, line 180: In this statement, an array subscript expression is either less than zero or greater than the largest value that can be represented by the size_t type. (badsubscript) ((InvalidationUserData *) entry)->dataP[-1] = ------------------------------------------------^ cc: Info: inval.c, line 202: In this statement, an array subscript expression is either less than zero or greater than the largest value that can be represented by the size_t type. (badsubscript) &((InvalidationUserData *) invalid)->dataP[-1]; -------------------------------------------------------------------^ There are some more warnings regarding the imcompatability between 'char' and 'unsigned char' which I do not regard as serious. Hoping to help in a way! -- Mit freundlichen Gruessen / With best regards Reiner Dassing
В списке pgsql-admin по дате отправления: