| From: | Job <Job(at)colliniconsulting(dot)com> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | R: Problem with row-level lock |
| Date: | 2019-06-21 08:40:35 |
| Message-ID: | 88EF58F000EC4B4684700C2AA3A73D7A082D27F19C07@W2008DC01.ColliniConsulting.lan |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Dear Adrian,
thank you for the reply!
>> i am struggling with a problem due, sometime, to a double concurrent update on the same row of a table.
>What is the error message you get?
We have no error, but the two queries, in "Lock wait", keep stucked for some minutes before completed.
Are there any parameters useful to "serialize" in some way two different Update queries - for the same field in the same row - arriving concurrently?
I was looking at the lock_timeout parameter: could it be what i am looking for?
Thank you!
Franco
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Karsten Hilbert | 2019-06-21 09:57:54 | Re: Row data is reflected in DETAIL message when constraints fail on insert/update |
| Previous Message | AYahorau | 2019-06-21 08:14:58 | Active connections are terminated because of small wal_sender_timeout |