Josh Berkus wrote: > 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
Anything that causes an ERROR in the final stages of a transaction commit will look like this. Maybe, for example, something tried to acquire more shared memory for something (serializable xact?) but that was already full because of lock objects. -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
