[Bucardo-general] Test Failures: Serialized Isolation
Greg Sabino Mullane
greg at endpoint.com
Wed Oct 24 16:08:48 UTC 2012
On Wed, Oct 24, 2012 at 09:05:49AM -0700, David E. Wheeler wrote:
...
> * Retry immediately with no sleep
> * If that fails, sleep for 1s and retry again
> * Keep repeating every 1s
> * Die after 10 or 50 or something.
No, I like the user-specified sleep. I know that on some busy systems, trying
every second is not optimal. As Jon says, I don't think we should stop either.
> +1 This makes sense. Also, the --retry option should no longer be needed, right?
Right. Because any other non-fatal error that might need retry should
be handled internally as well.
> We could add a test to run only on 8.4+ that mimics it using PL/pgSQL:
>
> david=# \set VERBOSITY verbose
> david=# DO $$BEGIN RAISE EXCEPTION 'Serialization error'
> USING ERRCODE = 'serialization_failure'; END $$;
> ERROR: 40001: Serialization error
> LOCATION: exec_stmt_raise, pl_exec.c:2840
Heh, nice!
--
Greg Sabino Mullane greg at endpoint.com
End Point Corporation
PGP Key: 0x14964AC8
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 163 bytes
Desc: not available
URL: <https://mail.endcrypt.com/pipermail/bucardo-general/attachments/20121024/880eb43f/attachment.sig>
More information about the Bucardo-general
mailing list