Allow setting DISABLE_SERVER_SIDE_CURSORS for PostgreSQL configurations about pretix HOT 3 CLOSED

I'm hesitant – yes, not much of an effort and easily doable, on the other hand there's so much more that could break on pgBouncer and I'm not sure we want to go down that route :\

from pretix.

I'm guessing except if you explicitly use PostgreSQL features that wouldn't work with transaction mode (cursors, prepared statements mostly) it should work, and it seems for now at least that we didn't encounter any problems except in that instance where Django/psycopg2 transparently uses cursors for you.

We'd be fine with a requirement for session pooling though if that's the official stance. Too bad for the extra resources we'd have to permanently allocate to Pretix instead of having them be distributed with the other apps using the DB, but nothing we can't handle.

from pretix.

Yeah. Would you be willing to create PR with the config flag?

from pretix.