Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 970D32E3835 for ; Tue, 5 Feb 2008 07:38:40 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 47214-04 for ; Tue, 5 Feb 2008 07:38:20 -0400 (AST) Received: from lists.commandprompt.com (host-159.commandprompt.net [207.173.203.159]) by postgresql.org (Postfix) with ESMTP id C61E32E3743 for ; Tue, 5 Feb 2008 07:38:34 -0400 (AST) Received: from perhan.alvh.no-ip.org (190-95-28-116.bk17-dsl.surnet.cl [190.95.28.116]) (authenticated bits=0) by lists.commandprompt.com (8.13.8/8.13.8) with ESMTP id m15BcJWw027688 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 5 Feb 2008 03:38:30 -0800 Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 4626E47BEB; Tue, 5 Feb 2008 08:37:59 -0300 (CLST) Date: Tue, 5 Feb 2008 08:37:59 -0300 From: Alvaro Herrera To: Mike Williams Cc: pgsql-admin@postgresql.org Subject: Re: "create implicit sequence" crashes postgres Message-ID: <20080205113759.GC32363@alvh.no-ip.org> References: <200802041726.01060.mike.williams@comodo.com> <6679.1202153472@sss.pgh.pa.us> <200802051104.07958.mike.williams@comodo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200802051104.07958.mike.williams@comodo.com> User-Agent: Mutt/1.5.17+20080114 (2008-01-14) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (lists.commandprompt.com [207.173.203.159]); Tue, 05 Feb 2008 03:38:31 -0800 (PST) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200802/26 X-Sequence-Number: 28100 Mike Williams wrote: > I have however found a "fix". We use hardened Gentoo everywhere, on all the > 64bit Xen VMs and 64bit proper server (that does not crash!), but not the 8.1 > VM as that is a 32bit Centos install thrown together as a dev environment. > Compiling postgresql non-hardened allows me to create any table I like, and > throw a couple hundred meg of data and schema at it in one go. I guess it would still be good to know why it crashes. I think the reason you're not getting a good backtrace is that you're attempting to get it from the client process, which is not the guilty one here. Same for the ulimit setting: you have to apply it to the session running postmaster, not psql. The core file should be located in your "data" directory. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support