New kind of crash?

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: New kind of crash?
Date: 2013-03-09 00:27:30
Message-ID: 513A81F2.5060409@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Folks,

This is one I've never seen before:

=> select generate_master_tables();
WARNING: AbortTransaction while in COMMIT state
PANIC: cannot abort transaction 9387287, it was already committed
PANIC: cannot abort transaction 9387287, it was already committed
The connection to the server was lost. Attempting reset: Failed.
Time: 42259.753 ms
!>

Interestingly, Postges came back up on its own after about a minute and
seems to be OK. The stored procedure in question is one which creates
about 600 tables. This actually exceeds max_locks_per_transaction, but
what happened above is not the normal failure for that.

Note that the tables were, in fact, created, and as far as I can tell
there's no corruption of the database.

--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Mark Kirkwood 2013-03-09 03:17:36 Re: New kind of crash?
Previous Message Josh Berkus 2013-03-08 23:27:34 Issue with range types and casts?