Re: database-level lockdown
| От | Tom Lane |
|---|---|
| Тема | Re: database-level lockdown |
| Дата | |
| Msg-id | 25231.1434050864@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | database-level lockdown (Filipe Pina <filipe.pina@impactzero.pt>) |
| Ответы |
Re: database-level lockdown
|
| Список | 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 по дате отправления: