Josh Berkus wrote:
> Folks,
>=20
> This is one I've never seen before:
>=20
> =3D> 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.
--=20
=C1lvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
