Re: database-level lockdown

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Filipe Pina <filipe(dot)pina(at)impactzero(dot)pt>
Cc: Postgresql General <pgsql-general(at)postgresql(dot)org>
Subject: Re: database-level lockdown
Date: 2015-06-11 19:27:44
Message-ID: 25231.1434050864@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Filipe Pina <filipe(dot)pina(at)impactzero(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2015-06-11 19:29:55 Re: GCC error and libmpfr.so.4 not found
Previous Message Jimmy Yih 2015-06-11 19:18:27 Re: GCC error and libmpfr.so.4 not found