Bug in Postgres support for search_path

Description: trying to use certain features of Postgres (like htables) when using a schema other than 'public' result in Postgres SQL errors.

Expect to see:

Queries which use hstore, when enabled, to succeed.

Actually see:

Error messages saying that public.hstore is not defined.

Core reason:

When 'public' is not part of the current search_path, then extensions defined in public are not able to be used by tables in a different schema.

Details:

I believe Heidi is over-writing the default search_path set by either the database or the user settings. (HeidiSQL is deciding the search path should be limited to *only* the schema they selected in the connection details.) This can lead to unexpected behavior.