Oi Euler, Vou postar a saída do gdb, desculpe pelo tamanho mas não sei qual parte deve ser importante.
-bash-3.2$ gdb /usr/local/pgsql-9.0.4/bin/postgres $PGDATA/core GNU gdb (GDB) Red Hat Enterprise Linux (7.0.1-23.el5_5.2) Copyright (C) 2009 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/local/pgsql-9.0.4/bin/postgres...done. "/bd/postgres-9.0.4/core" is not a core dump: Is a directory (gdb) ERROR: invalid value for parameter "client_encoding": "undefined" STATEMENT: SET client_encoding TO Undefined ERROR: invalid value for parameter "client_encoding": "undefined" STATEMENT: SET client_encoding TO Undefined ERROR: invalid value for parameter "client_encoding": "undefined" STATEMENT: SET client_encoding TO Undefined ERROR: invalid value for parameter "client_encoding": "undefined" STATEMENT: SET client_encoding TO Undefined ERROR: invalid value for parameter "client_encoding": "undefined" STATEMENT: SET client_encoding TO Undefined ERROR: invalid value for parameter "client_encoding": "undefined" STATEMENT: SET client_encoding TO Undefined ERROR: invalid value for parameter "client_encoding": "undefined" STATEMENT: SET client_encoding TO Undefined ERROR: invalid value for parameter "client_encoding": "undefined" STATEMENT: SET client_encoding TO Undefined ERROR: invalid value for parameter "client_encoding": "undefined" STATEMENT: SET client_encoding TO Undefined LOG: unexpected EOF on client connection LOG: unexpected EOF on client connection LOG: unexpected EOF on client connection LOG: unexpected EOF on client connection LOG: unexpected EOF on client connection LOG: server process (PID 11467) was terminated by signal 11: Segmentation fault LOG: terminating any other active server processes WARNING: terminating connection because of crash of another server process DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. HINT: In a moment you should be able to reconnect to the database and repeat your command. WARNING: terminating connection because of crash of another server process DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. HINT: In a moment you should be able to reconnect to the database and repeat your command. LOG: all server processes terminated; reinitializing LOG: database system was interrupted; last known up at 2011-08-26 11:42:25 BRT LOG: database system was not properly shut down; automatic recovery in progress LOG: consistent recovery state reached at 23/F5FF1880 LOG: redo starts at 23/F5FF1880 FATAL: the database system is in recovery mode LOG: record with zero length at 23/F60FD748 LOG: redo done at 23/F60FD708 LOG: last completed transaction was at log time 2011-08-26 11:45:49.067268-03 LOG: autovacuum launcher started LOG: database system is ready to accept connections ERROR: invalid value for parameter "client_encoding": "undefined" STATEMENT: SET client_encoding TO Undefined ERROR: invalid value for parameter "client_encoding": "undefined" STATEMENT: SET client_encoding TO Undefined ERROR: invalid value for parameter "client_encoding": "undefined" STATEMENT: SET client_encoding TO Undefined bERROR: invalid value for parameter "client_encoding": "undefined" STATEMENT: SET client_encoding TO Undefined t No stack. (gdb) ERROR: invalid value for parameter "client_encoding": "undefined" STATEMENT: SET client_encoding TO Undefined ERROR: invalid value for parameter "client_encoding": "undefined" STATEMENT: SET client_encoding TO Undefined bt No stack. (gdb) ERROR: invalid value for parameter "client_encoding": "undefined" STATEMENT: SET client_encoding TO Undefined ERROR: invalid value for parameter "client_encoding": "undefined" STATEMENT: SET client_encoding TO Undefined quiERROR: invalid value for parameter "client_encoding": "undefined" STATEMENT: SET client_encoding TO Undefined t -bash-3.2$ ERROR: invalid value for parameter "client_encoding": "undefined" STATEMENT: SET client_encoding TO Undefined -bash-3.2$ /usr/local/pgsql-9.0.4/bin/pg_ctl start -D $ERROR: invalid value for parameter "client_encoding": "undefined" STATEMENT: SET client_encoding TO Undefined /usr/local/pgsql-9.0.4/bin/pg_ctl stop -D $PGDATA waiting for server to shut down....LOG: received smart shutdown request LOG: autovacuum launcher shutting down FATAL: the database system is shutting down FATAL: the database system is shutting down FATAL: the database system is shutting down FATAL: the database system is shutting down ..ERROR: invalid value for parameter "client_encoding": "undefined" STATEMENT: SET client_encoding TO Undefined LOG: shutting down LOG: database system is shut down done []s -- ================================================= Diogo Borsoi Mobile: +55 12 91436960 http://br.linkedin.com/in/diborsoi http://diborsoi.wordpress.com/ ================================================= 2011/8/26 Diogo Borsoi <[email protected]>: > Oi Euler, > > > 2011/8/26 Euler Taveira de Oliveira <[email protected]>: >> Verifique com o comando 'pg_config --configure' se a opção --enable-debug não >> foi especificada. Se foi, vide os passos abaixo, senão: >> > > Não foi compilado com opção --enable-debug, vou recompilar. > '--prefix=/usr/local/pgsql-9.0.4' '--with-perl' '--with-python' > '--with-krb5' '--with-openssl' '--with-pgport=5434' > >> Seria útil se (i) recompilasse com --enable-debug para que pudéssemos >> encontrar o ponto do possível problema ou (ii) instalar com as mesmas opções >> do original (vide pg_config --configure) + enable-debug em outro local só >> para >> investigarmos o problema. >> > > A compilação está parecida ao PG 8.2.5, a não ser pelo fato do porta > que foi alterada e o acréscimo do LDFLAGS. > '--prefix=/usr/local/pgsql' '--with-perl' '--with-python' > '--with-krb5' '--with-openssl' 'LDFLAGS=-lstdc++' > >> Vale ressaltar que esta opção aumenta um pouco o tamanho dos binários >> produzidos mas não influi na performance dos mesmos. >> > > Ok, obrigado. > >> Quanto a obter o _stack trace_, siga os passos: >> >> # su - postgres >> $ ulimit -c unlimited >> $ /path/to/pg_ctl start -D $PGDATA >> (executar os procedimentos para produzir a queda do servidor) >> $ gdb /path/to/postgres $PGDATA/core >> (gdb) bt >> > > Farei isso ao final da recompilação. > > > []s > >> >> -- >> Euler Taveira de Oliveira - Timbira http://www.timbira.com.br/ >> PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento >> _______________________________________________ >> pgbr-geral mailing list >> [email protected] >> https://listas.postgresql.org.br/cgi-bin/mailman/listinfo/pgbr-geral >> > _______________________________________________ pgbr-geral mailing list [email protected] https://listas.postgresql.org.br/cgi-bin/mailman/listinfo/pgbr-geral
