From: Chris Rienzo Date: Tue, 7 Oct 2014 13:33:19 +0000 (-0400) Subject: switch_pgsql.c switch_pgsql_next_result_timed() was using switch_time_now() for... X-Git-Tag: v1.4.10~1^2~14 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=4a5e36d63e11c6e7a7fb0cf2e874cdd4479ece55;p=thirdparty%2Ffreeswitch.git switch_pgsql.c switch_pgsql_next_result_timed() was using switch_time_now() for start time and switch_micro_time_now() for current time. These are different time sources that may not be in sync and could cause the query to timeout prematurely. --- diff --git a/src/switch_pgsql.c b/src/switch_pgsql.c index ccf64d1503..74eea5cb8e 100644 --- a/src/switch_pgsql.c +++ b/src/switch_pgsql.c @@ -305,7 +305,7 @@ SWITCH_DECLARE(switch_pgsql_status_t) switch_pgsql_next_result_timed(switch_pgsq if (PQisBusy(handle->con)) { /* Wait for a result to become available, up to msec milliseconds */ - start = switch_time_now(); + start = switch_micro_time_now(); while((ctime = switch_micro_time_now()) - start <= usec) { int wait_time = (usec - (ctime - start)) / 1000; fds[0].fd = handle->sock;