[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pgsql-hackers
Subject:    Re: [HACKERS] [ADMIN] Postgres server goes in recovery mode repeteadly
From:       Tom Lane <tgl () sss ! pgh ! pa ! us>
Date:       2009-09-29 16:28:03
Message-ID: 11214.1254241683 () sss ! pgh ! pa ! us
[Download RAW message or body]

kunal sharma <ksharma.linux@gmail.com> writes:
>         We are using Postgres 8.4 and its been found going into recovery

8.4.what?  (If not 8.4.1, an update would be the first thing to try.)

> Checking the logs I found that theres a segmentation fault ,

> Sep 26 05:39:54 pace kernel: postgres[28694]: segfault at 0000000000000030
> rip 000000000066ba8c rsp 00007fffd364da30 error 4

> gdb dump shows this

> Reading symbols from /lib64/libdl.so.2...done.
> Loaded symbols for /lib64/libdl.so.2
> Reading symbols from /lib64/libm.so.6...done.
> Loaded symbols for /lib64/libm.so.6
> Reading symbols from /lib64/libc.so.6...done.
> Loaded symbols for /lib64/libc.so.6
> Reading symbols from /lib64/ld-linux-x86-64.so.2...done.
> Loaded symbols for /lib64/ld-linux-x86-64.so.2
> Reading symbols from /lib64/libnss_files.so.2...done.
> Loaded symbols for /lib64/libnss_files.so.2
> 0x00002ad6d7b8c2b3 in __select_nocancel () from /lib64/libc.so.6
> (gdb)

A segfault inside select() seems fairly unlikely.  I suspect that you
used the wrong executable or otherwise got the wrong result here.
Please double-check, and next time show the whole stack trace ("bt")
not just the top function.

			regards, tom lane

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
[prev in list] [next in list] [prev in thread] [next in thread]