Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 8B2302E36BE for ; Mon, 4 Feb 2008 15:35:25 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 13597-01-10 for ; Mon, 4 Feb 2008 15:35:11 -0400 (AST) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 40A562E370C for ; Mon, 4 Feb 2008 15:31:27 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id m14JVCOm006680; Mon, 4 Feb 2008 14:31:12 -0500 (EST) To: Mike Williams cc: pgsql-admin@postgresql.org Subject: Re: "create implicit sequence" crashes postgres In-reply-to: <200802041726.01060.mike.williams@comodo.com> References: <200802041726.01060.mike.williams@comodo.com> Comments: In-reply-to Mike Williams message dated "Mon, 04 Feb 2008 17:26:00 +0000" Date: Mon, 04 Feb 2008 14:31:12 -0500 Message-ID: <6679.1202153472@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200802/14 X-Sequence-Number: 28088 Mike Williams writes: > We're trying to move off a single VM running postgres 8.1 to a newer more > powerful pair of VMs with a DRBD mirror for storage and postgres 8.2. > But, every attempt to dump the data from 8.1.x into 8.2.6 fails, and fails > exactly the same way. > And any SQL to create a table with more than 24, or 25 (can't remember off top > of my head) characters long, with a serial column, causes this crash: > Feb 4 17:00:03 mcsql1 postgres[6639]: [23-1] NOTICE: CREATE TABLE will > create implicit sequence "billing_transaction_items_id_seq" for serial column > Feb 4 17:00:03 mcsql1 postgres[6639]: [23-2] "billing_transaction_items.id" > Feb 4 17:00:03 mcsql1 postgres[6377]: [4-1] LOG: server process (PID 6639) > was terminated by signal 11 > The only comonality between those that crash is that they're all 64bit Xen > VMs, so far non-VM servers don't crash. But nothing anywhere I can find even > vaguely hints at problems running Postgres under Xen. News to me too. Can you get a stack trace from the crash? Can you extract a small test case from your dump script, so people can try it elsewhere? regards, tom lane