Re: database-level lockdown - Mailing list pgsql-general

From Tom Lane
Subject Re: database-level lockdown
Date
Msg-id 25231.1434050864@sss.pgh.pa.us
Whole thread Raw
In response to database-level lockdown  (Filipe Pina <filipe.pina@impactzero.pt>)
Responses Re: database-level lockdown  (Filipe Pina <filipe.pina@impactzero.pt>)
List pgsql-general
Filipe Pina <filipe.pina@impactzero.pt> writes:
> It will try 5 times to execute each instruction (in case of
> OperationError) and in the last one it will raise the last error it
> received, aborting.

> Now my problem is that aborting for the last try (on a restartable
> error - OperationalError code 40001) is not an option... It simply
> needs to get through, locking whatever other processes and queries it
> needs.

I think you need to reconsider your objectives.  What if two or more
transactions are repeatedly failing and retrying, perhaps because they
conflict?  They can't all forcibly win.

            regards, tom lane


pgsql-general by date:

Previous
From: Jimmy Yih
Date:
Subject: Re: GCC error and libmpfr.so.4 not found
Next
From: Tom Lane
Date:
Subject: Re: GCC error and libmpfr.so.4 not found