X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id C2BCC9FBB35 for ; Fri, 25 Aug 2006 12:24:52 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 77410-10 for ; Fri, 25 Aug 2006 12:24:47 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from lists.commandprompt.com (host-130.commandprompt.net [207.173.203.130]) by postgresql.org (Postfix) with ESMTP id 21E6B9FBB25 for ; Fri, 25 Aug 2006 12:24:46 -0300 (ADT) Received: from alvh.no-ip.org (201-221-200-187.bk11-dsl.surnet.cl [201.221.200.187]) (authenticated bits=0) by lists.commandprompt.com (8.13.7/8.13.6) with ESMTP id k7PFOT85030011; Fri, 25 Aug 2006 08:24:30 -0700 Received: by alvh.no-ip.org (Postfix, from userid 1000) id 717B1C2DC63; Fri, 25 Aug 2006 11:24:13 -0400 (CLT) Date: Fri, 25 Aug 2006 11:24:13 -0400 From: Alvaro Herrera To: Tom Lane Cc: Donald Fraser , "[ADMIN]" Subject: Re: Strange message followed by server crash Message-ID: <20060825152413.GG14622@alvh.no-ip.org> Mail-Followup-To: Tom Lane , Donald Fraser , "[ADMIN]" References: <003401c6c837$8dc6cb90$7d64a8c0@demolish1> <23160.1156513462@sss.pgh.pa.us> <008c01c6c855$35f6cd20$7d64a8c0@demolish1> <24548.1156518324@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <24548.1156518324@sss.pgh.pa.us> User-Agent: Mutt/1.5.12-2006-07-14 X-Virus-Scanned: ClamAV version 0.88.3, clamav-milter version 0.88.3 on projects.commandprompt.com X-Virus-Status: Clean X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (lists.commandprompt.com [192.168.2.159]); Fri, 25 Aug 2006 08:24:30 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.332 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200608/289 X-Sequence-Number: 22832 Tom Lane wrote: > "Donald Fraser" writes: > > "Tom Lane" writes: > >> Given that this sounds like it won't be easy to reproduce, I'm hoping > >> you have a core file left from that and can get a stack trace from it. > > > Where would I look for a core file? > > There's nothing unusual in the data directory, nothing in the /tmp = > > directory? > > Normally it would go into the $PGDATA/base/NNN subdirectory for the > database the backend was connected to. A very few systems (OS X for > instance) drop cores into a dedicated system-wide directory called > /cores or some such. Note that on recent versions of Linux you can modify both the file name and the directory where it's saved, by modifying /proc/sys/kernel/core_pattern (or the deprecated /proc/sys/kernel/core_uses_pid). See core(5) for details. -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc.