Support transactional testing for fast tests with shared setup about pytest-postgresql

[fizyk]

I think that would be something worth considering.

As I'm not sure when I'll find the time to work on this, but you're welcome to create a pull request.
One thing to consider would be to put documentation warnings that the same connection has to be sued throughout the test suite as any new connection code will make would be outside of the transaction

[fizyk]

@efagerberg Could you take a look at a pr I'm baking? #407 it's not transactional testing per se, as it makes use of database templates instead. This approach sped up test in our project 4 times.

[efagerberg]

I think having a transactional fixture is preferred. In my case I have noticed that sometimes the postgres server fails to start up leading to flakey test suits, just having one db that is more global in pytest would reduce the setup time for each test and hopefully make the test suite less brittle.

[fizyk]

Addressed by #407 / #393