X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id ED943D1B524 for ; Thu, 30 Oct 2003 19:14:10 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 11581-08 for ; Thu, 30 Oct 2003 15:13:41 -0400 (AST) Received: from serwer.skawsoft.com.pl (serwer.skawsoft.com.pl [213.25.37.66]) by svr1.postgresql.org (Postfix) with ESMTP id DD8FDD1B4F4 for ; Thu, 30 Oct 2003 15:13:39 -0400 (AST) Received: from klaster.net (core-1.citynet.pl [80.48.135.69]) by serwer.skawsoft.com.pl (Postfix) with ESMTP id 235682B3CE; Thu, 30 Oct 2003 20:13:33 +0100 (CET) Message-ID: <3FA16305.7000202@klaster.net> Date: Thu, 30 Oct 2003 20:14:13 +0100 From: Tomasz Myrta User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; pl-PL; rv:1.5) Gecko/20030916 X-Accept-Language: pl, en-us, en MIME-Version: 1.0 To: Jan Wieck Cc: Lista dyskusyjna pgsql-sql Subject: Re: strange postgresql failure References: <3FA0F6E9.5060404@klaster.net> <3FA103AF.1000006@klaster.net> <3FA14B78.4030904@Yahoo.com> In-Reply-To: <3FA14B78.4030904@Yahoo.com> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/406 X-Sequence-Number: 15806 Dnia 2003-10-30 18:33, Użytkownik Jan Wieck napisał: > There is, sort of ... it's called "core" and if your backend and C > function shared object have been compiled with symbol information you > can use a debugger to get a stack trace and look at variables. If that's > not "human readable" ... well ... I suppose I'm not human. I know I can load core into gdb... I thought about some kind of message before postgres restarts. I read in syslog that backend terminated with segmentation fault signal and probably corrupted shared memory. It didn't help me to find what really happened. I was wondering if it is possible to know the real reason of restart and leave some message in syslog just before postgres restarts. Regards, Tomasz Myrta