From: | David Greco <David_Greco(at)harte-hanks(dot)com> |
---|---|
To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | auto_explain & FDW |
Date: | 2013-06-27 12:24:14 |
Message-ID: | 187F6C10D2931A4386EE8E58E13857F63043867C@BY2PRD0811MB415.namprd08.prod.outlook.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
In my development environment, I am using the auto_explain module to help debug queries the developers complain about being slow. I am also using the oracle_fdw to perform queries against some oracle servers. These queries are generally very slow and the application allows them to be. The trouble is that it appears auto_explain kicks in on the query to try and explain them when they take longer than the configured threshold. In this particular case, the Oracle user is very locked down and cannot actually perform an explain. Therefore an error gets raised to the client.
I would suggest one of two things- either make the error that gets raised simply be a notice/warning, or preferably just add an option to auto_explain to enable/disable its operation on queries involving foreign servers.
Any thoughts?
~Dave Greco
From | Date | Subject | |
---|---|---|---|
Next Message | Suzuki Hironobu | 2013-06-27 12:41:52 | Re: Migration from DB2 to PostgreSQL-TIMESTAMP(arg1,arg1) |
Previous Message | Daniel Cristian Cruz | 2013-06-27 12:11:39 | Re: Migration from DB2 to PostgreSQL-TIMESTAMP(arg1,arg1) |