Hi

I found a small problem in the pg_session_variables function. I expected syscache to be flushed for recent catalog changes

before any usage of this function. But it is not always true. When I used the DCATCACHE_FORCE_RELEASE build option, I got

different results from isolation tests. Fix is simple - just call AcceptInvalidationMessages(); before touching syscache in this

function.

Note: pg_session_variables is a debug function - it shows entries of a hash table with session variables used in the current session.

The result's attribute with information if the entry is related to a valid or to invalid value (related tuple in pg_variable exists or not) was not correct.

Regards

Pavel