Mitu Verma <mitu.verma@ericsson.com> writes:
> I am not sure if it is a postgres issue or not, so need your help in that.
Well, it looks like you've got two concurrent transactions trying to
insert the exact same data:
> 16384 | fm_db_CollectCCN | 20714 | 16391 | mmsuper | | ::1 | |
19540
> | 2014-07-07 19:10:09.295565+02 | 2014-07-07 19:10:09.311701+02 | 2014-07-07 19:10:09.311701+02 | f | INSERT
INTOev
> entLogEntry (object, method, bgwUser, time, realUser, host, application, tableIndex ) VALUES (E'Server', E'Start',
E'bgw'
> , E'20140512122404', NULL, NULL, NULL, 539 )
> 16384 | fm_db_CollectCCN | 20819 | 16391 | mmsuper | | ::1 | |
19602
> | 2014-07-07 19:10:45.18688+02 | 2014-07-07 19:10:45.202903+02 | 2014-07-07 19:10:45.202903+02 | f | INSERT
INTOev
> entLogEntry (object, method, bgwUser, time, realUser, host, application, tableIndex ) VALUES (E'Server', E'Start',
E'bgw'
> , E'20140512122404', NULL, NULL, NULL, 539 )
Presumably this is falling foul of a unique index on the table.
The second one is going to block until the first one either
commits or rolls back.
regards, tom lane