| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | hargudekishor(at)gmail(dot)com |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #14273: Tuple concurently updated error while creating function using async call from node js with postgresq |
| Date: | 2016-08-02 18:00:11 |
| Message-ID: | 20160802180011.GA556096@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
hargudekishor(at)gmail(dot)com wrote:
> 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".
Yeah, this is known. We haven't worried too much, because the use case
seems thin: why are you deleting and creating the function over and
over? Wouldn't it be better to create the function once and be done
with it?
> And because of this error our node js application is getting
> terminated.which is not affordable to us.
Surely the application should be able to do something else upon
receiving an error, rather than crashing.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2016-08-02 18:06:30 | Re: BUG #12884: configure script fails on a platform with /tmp directory read only |
| Previous Message | Peter Eisentraut | 2016-08-02 17:48:10 | Re: BUG #13810: cursor_to_xml ignores tableforest parameter |