Re: "create implicit sequence" crashes postgres

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Mike Williams <mike(dot)williams(at)comodo(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: "create implicit sequence" crashes postgres
Date: 2008-02-04 19:31:12
Message-ID: 6679.1202153472@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Mike Williams <mike(dot)williams(at)comodo(dot)com> 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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Rainer Spittel 2008-02-04 20:07:26 performance on selecting a row in large tables
Previous Message Mike Williams 2008-02-04 17:26:00 "create implicit sequence" crashes postgres