Received: from localhost (unknown [200.46.204.184]) by developer.postgresql.org (Postfix) with ESMTP id 2191C2E00F7 for ; Tue, 29 Apr 2008 03:05:53 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 52625-01-6 for ; Tue, 29 Apr 2008 03:05:46 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.28]) by developer.postgresql.org (Postfix) with ESMTP id 6D8F72E005E for ; Tue, 29 Apr 2008 03:03:31 -0300 (ADT) Received: by yw-out-2324.google.com with SMTP id 5so1602252ywb.73 for ; Mon, 28 Apr 2008 23:03:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=LFM8TpVnx04+IEw0PNcBIrPdn/bLqBSCsZFPgGfnmYQ=; b=BGkE3gpD1iaSaTPc5w6lpis5unRKKA4MAln7Dk4npWxXS7A9c9n/Tut5TZgTBao6YJsPnWhfdAXD9yHCgOKsl8rgIkAphaPZ51WU5MsOowI713XLUYfwE7mVFln9oRH0yAwAQrqgFigKlzAsw98RNt3sVETd4RTNc9YviggJUYU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ZLIIe09qnXMfqhQTVtn3sHx8NyT3C9pz85nbJaRu40jUEp97NwnPChOblEQlWiUTciF3hZo2y/FsnniK+R7ivp1V1BsEA1t4urH6jJmPJepHl65A5ARyg32jPDgS5j+UzYJIugXMPaATF5YSwWdcu0VP37OfPs1ULKI2UhGDqno= Received: by 10.151.83.12 with SMTP id k12mr4716065ybl.1.1209449003067; Mon, 28 Apr 2008 23:03:23 -0700 (PDT) Received: by 10.151.84.7 with HTTP; Mon, 28 Apr 2008 23:03:23 -0700 (PDT) Message-ID: <2e78013d0804282303s48be0a09m5b533bb3b0d0243@mail.gmail.com> Date: Tue, 29 Apr 2008 11:33:23 +0530 From: "Pavan Deolasee" To: "Peter Koczan" Subject: Re: Bus error in postgres 8.3 Cc: "pgsql-admin@postgresql.org" In-Reply-To: <4544e0330804282205odfcac5al6bca78bd27c8751b@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4544e0330804282205odfcac5al6bca78bd27c8751b@mail.gmail.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200804/275 X-Sequence-Number: 29039 On Tue, Apr 29, 2008 at 10:35 AM, Peter Koczan wrote: > > I'm going to try to force a crash on my test server to see if I can > find out anything more. Does anyone know how to get useful debugging > info at the time of the crash? I don't think I have things set to dump > core anywhere, but that and/or stack traces would be nice (especially > for child processes). > Yeah, a stack trace and if possible, a self contained test case to reproduce the bug would help. If you are using a custom build, then using a debug build would help a lot too. Thanks, Pavan -- Pavan Deolasee EnterpriseDB http://www.enterprisedb.com