Postgres support & delays with exponential backoff and jitter

[nesl247]

Hi,

We switched from MySQL to Postgres a few years ago, but didn't want to give up this feature set. We're still on V2, which I know isn't maintained, plus we haven't written all the tests for it, hence why I'm not submitting a PR. But I wanted to point out the branch in case anyone else could make use of it / wants to take over getting this merged into mainline. If once we finally upgrade to Doctrine ORM 3 / DBAL 4, we'll try to work towards submitting a few PRs for the various features.

https://github.com/nesl247/doctrine-mysql-come-back/tree/postgres

And thanks to #59 for the inspiration on the implementation for delays.

Thanks!

[Jean85]

Hey @nesl247, thank you for reporting this! In theory, the 2.x branch IS still maintained, since we're still using it a lot in our company, due to the impossibility to use DBAL 3 in many cases.

[nesl247]

That's great news. Would it be helpful for us to submit a PR for the changes? Would it be accepted for the 2.x branch? Given we don't use 3.x I think someone else would have to port the change there.

[Jean85]

A PR is more than welcome, but I would suggest you to split it in multiple ones, since it looks like your fork is mixing multiple new features in a single commit.

As for the porting, no worries, I can try to do it; target the branch that you prefer.

[nesl247]

A PR is more than welcome, but I would suggest you to split it in multiple ones, since it looks like your fork is mixing multiple new features in a single commit.

As for the porting, no worries, I can try to do it; target the branch that you prefer.

Yep, absolutely. We're mixing them since we're using them in production this way. But I can easily split it to get it merged upstream. I'll try to work on submitting some when I have some more time.

Thanks!