On 03/08/2013 07:27 PM, Alvaro Herrera wrote:
> 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.
>
Well, is it worth trying to reproduce and diagnose?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com