[#1011347] Documentation is not clear about server_reset_query within transaction pooling

View Trackers | Bugs | Download .csv | Monitor

Date:
2013-07-24 10:34
Priority:
3
State:
Open
Submitted by:
Luis Bosque (luisico)
Assigned to:
Nobody (None)
Category:
None
Group:
None
Resolution:
None
 
Summary:
Documentation is not clear about server_reset_query within transaction pooling

Detailed description
Documentation says that setting or resetting variables within a transaction pooling mode is not supported. Also that using server_reset_query within transaction pooling mode is not needed.

That's not entirely true. It's true that setting custom variables within this pooling mode won't survive in the pool but, as long as, a server connection is still alive from pgbouncer to the postgres, the set variables are preserved.

So, for example, if a user@db sets a variable and after that (and before the server reaches the idle_server_timeout) another user@db runs a query the previous set variable is going to be still present.

I believe that the documentation should be a bit more clear about that.

Cheers

Followup

No Followups Have Been Posted

Attached Files:

Changes:

No Changes Have Been Made to This Item

Powered By FusionForge