On 01/11/2017 04:31 PM, Patrick B wrote:
2017-01-12 13:23 GMT+13:00 Adrian Klaver <adrian.klaver@xxxxxxxxxxx
<mailto:adrian.klaver@xxxxxxxxxxx>>:
It is not the same DB if it is on two different servers not
connected by replication. More to the point statement_timeout is a
client connection setting, so is the client you use to connect to
server2 the same as the one you use for server1?
Is AWS being 'helpful' and setting a timeout?
Is there anything in the log before the ERROR shown above that
indicates something is setting statement_timeout?
<mailto:adrian.klaver@xxxxxxxxxxx>
Same database, different database servers; server1 is the old Master
server and I'm using it to compare.
Are you actually running 9.2 on AWS, as the lowest version I see is 9.3.
Might be helpful to run the below on server2:
select * from pg_settings where name='statement_timeout';
and see what source says:
https://www.postgresql.org/docs/9.2/static/view-pg-settings.html
It is not the client, because if I run the query manually using explain
analyze i get the error:
live_db=> explain analyze
SELECT DISTINCT id0
FROM
(SELECT
[...]
ERROR: canceling statement due to statement timeout
just a remind that on server1 works, but on server2 it doesn't.
--
Adrian Klaver
adrian.klaver@xxxxxxxxxxx
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
