BUG #14273: Tuple concurently updated error while creating function using async call from node js with postgresq

The following bug has been logged on the website:

Bug reference: 14273
Logged by: Kishor Hargude
Email address: hargudekishor(at)gmail(dot)com
PostgreSQL version: 9.4.8
Operating system: Ubuntu
Description:

Hi,

I am facing a strange issue on postgresql-9.4.8.

below is the description of the issue.

We have connected our node js application with postgresql-9.4.8.We have
several functions which are getting created in database using async call
from nodejs to postgresql server.but while creating those functions ,We are
encountered a error of "Tuple concurrently updated".And because of this
error our node js application is getting terminated.which is not affordable
to us.

Below is the exact error lines from node js app logs.

[error: tuple concurrently updated]
name: 'error',
length: 83,
severity: 'ERROR',
code: 'XX000',
detail: undefined,
hint: undefined,
position: undefined,
internalPosition: undefined,
internalQuery: undefined,
where: undefined,
schema: undefined,
table: undefined,
column: undefined,
dataType: undefined,
constraint: undefined,
file: 'heapam.c',
line: '4097',
routine: 'simple_heap_update' }
error: tuple concurrently updated
at Connection.parseE
(/var/www/tea/tea/gamma/node_modules/pg/lib/connection.js:539:11)
at Connection.parseMessage
(/var/www/tea/tea/gamma/node_modules/pg/lib/connection.js:366:17)
at Socket.<anonymous>
(/var/www/tea/tea/gamma/node_modules/pg/lib/connection.js:105:22)
at Socket.emit (events.js:95:17)
at Socket.<anonymous> (_stream_readable.js:764:14)
at Socket.emit (events.js:92:17)
at emitReadable_ (_stream_readable.js:426:10)
at emitReadable (_stream_readable.js:422:5)
at readableAddChunk (_stream_readable.js:165:9)
at Socket.Readable.push (_stream_readable.js:127:10)
at TCP.onread (net.js:528:21)

********************************************
Below is the exact error lines from PG logs.

tuple concurrently updated
2016-08-02 10:13:06 IST:[unknown]:teadbuser:teadb_mixdbSTATEMENT: DROP
FUNCTION IF EXISTS get_changeoverview_new_added_components(integer,
character varying,character varying,character varying, numeric, numeric);

CREATE OR REPLACE FUNCTION
get_changeoverview_new_added_components(
.
.
.
.

We tried to execute those function by setting transaction_isolation to
serializable but encountered same issue.

Please suggest me that,How can I bypass this error...OR is it a bug about
severity of message ("tuple concurrently updated")on this kind of issue
.Should it be only warning ?

--
Kishor.