Re: [BUGS] BUG #14531: server process (PID 12714) was terminated by signal 11: Segmentation fault
От | Tom Lane |
---|---|
Тема | Re: [BUGS] BUG #14531: server process (PID 12714) was terminated by signal 11: Segmentation fault |
Дата | |
Msg-id | 21590.1486499428@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: [BUGS] BUG #14531: server process (PID 12714) was terminated bysignal 11: Segmentation fault (NAVEEN CHALIMETI <naveenallin@gmail.com>) |
Ответы |
Re: [BUGS] BUG #14531: server process (PID 12714) was terminated bysignal 11: Segmentation fault
|
Список | pgsql-bugs |
NAVEEN CHALIMETI <naveenallin@gmail.com> writes: > Thanks for your reply firstly. > I did not mention anything about logs thinking the back trace would be > enough to solve the issue. Sorry for that. > I have enabled the *log_statement=all* already and each time it gives > different queries. But until now i have seen postmaster crashed during > SELECT query. > ... > The crash is reproducible with different queries. Hm. Have you looked at more than one core dump? Is it always the same backtrace? Those queries don't look particularly exciting, so I'm now thinking the problem is something unusual. Do you have any nondefault extensions installed? Maybe you built the server with some unusual options? I dislike blaming hardware problems, but we shouldn't rule out that possibility either, unless you're seeing this on more than one machine. regards, tom lane -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
В списке pgsql-bugs по дате отправления: