Re: pq_recvbuf: unexpected EOF
От | David Link |
---|---|
Тема | Re: pq_recvbuf: unexpected EOF |
Дата | |
Msg-id | 20030425213220.31509.qmail@web13501.mail.yahoo.com обсуждение исходный текст |
Ответ на | Re: pq_recvbuf: unexpected EOF (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: pq_recvbuf: unexpected EOF
|
Список | pgsql-general |
Running with ulimit ... echo "setting max user processes to unlimited..." ulimit -u unlimited echo -n "$PSQL_START" su -l postgres -s /bin/sh -c "$PGLIB/bin/pg_ctl -D $PGDATA -p $PGLIB/bin/postmaster -o '-i' start > $PGDATA/log/syslog 2>&1" < /dev/null but still no core. I can't product that bt. Any suggestions? --- Tom Lane <tgl@sss.pgh.pa.us> wrote: > David Link <dvlink@yahoo.com> writes: > > [4] LOG: pq_recvbuf: unexpected EOF on client connection > > [4] LOG: server process (pid 28353) was terminated by signal 11 > > [5] LOG: terminating any other active server processes > > That's not what I would call a "scaling issue" :-( > > Can you get us a stack backtrace from the crashed backend? Since > this is linux, you probably aren't getting core files (look for > $PGDATA/base/nnnnnn/core) --- if not, restart the postmaster under > "ulimit -c unlimited" (best to add that to its startup script). > Once you have a core file, try > > gdb /path/to/postgres-executable /path/to/core-file > gdb> bt > gdb> p debug_query_string > gdb> quit > > It would also be worthwhile to enable log_statement in > postgresql.conf > so that you can get more info on the command or series of commands > that > leads up to the crash. > > Also, if you compiled Postgres yourself, it would be worth the > trouble > to recompile with --enable-debug and --enable-cassert added to > whatever > configure parameters you used before. I'm not sure what it takes to > do > the equivalent in an RPM-based installation. > > regards, tom lane __________________________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo http://search.yahoo.com
В списке pgsql-general по дате отправления: