[GENERAL] Retrying transactions in serializable isolation level

elated to concurrency. I spent 4 hours trying to find a code snippet that does this. So far I've been unsuccessful. Any precisions would be greatly appreciated. Thanks, Laurent Birtz ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster

[TLM] [GENERAL] Retrying transactions in serializable isolation level

elated to concurrency. I spent 4 hours trying to find a code snippet that does this. So far I've been unsuccessful. Any precisions would be greatly appreciated. Thanks, Laurent Birtz ---(end of broadcast)--- TIP 2:

[GENERAL] Forcibly vacating locks

gres connection when the watchdog triggers. Thanks a lot for any response! Laurent Birtz -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] Forcibly vacating locks

Bruce Momjian wrote: Laurent Birtz wrote: Hello, I am using Postgres in a high-availability environment and I'd like to know whether Postgres has provisions to kick off a misbehaving client that has obtained an advisory lock on the database and won't release it in a timely fashion

Re: [GENERAL] Forcibly vacating locks

e next few days. Yea, I might be wrong. I think you're very right. Don't ever want to see locks disappearing because of a timeout, sorry Laurent. OK, thanks all for the replies. Laurent Birtz -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to