PgAdmin runs the query SELECT set_config('bytea_output', 'hex', false) FROM pg_show_all_settings() WHERE name = 'bytea_output';. I'm pretty sure this is just an attempt to avoid checking the version number, and who on earth is running PG < 9.0 at this point, but we have to support the bad queries too.
Currently we only handle set_config when there is no FROM or WHERE clause. We'll need to figure out how to handle this, while returning the correct number of rows to the client, and making sure we properly reset when the connection is checked back into the pool.
PgAdmin runs the query
SELECT set_config('bytea_output', 'hex', false) FROM pg_show_all_settings() WHERE name = 'bytea_output';. I'm pretty sure this is just an attempt to avoid checking the version number, and who on earth is running PG < 9.0 at this point, but we have to support the bad queries too.Currently we only handle
set_configwhen there is no FROM or WHERE clause. We'll need to figure out how to handle this, while returning the correct number of rows to the client, and making sure we properly reset when the connection is checked back into the pool.