[COMMITTERS] npgsql - Npgsql2: Fixed possible datareader leak if the test fail.

2012-11-18 Thread User Fxjr
Log Message: --- Fixed possible datareader leak if the test fail. The datareader wouldn't be closed until it was collected. Modified Files: -- Npgsql2/testsuite/noninteractive/NUnit20: CommandTests.cs (r1.49 -> r1.50) (http://cvs.pgfoundry.org/cgi-bin/cvs

[COMMITTERS] pgsql: Assert that WaitLatch's timeout is not more than INT_MAX millise

2012-11-18 Thread Tom Lane
Assert that WaitLatch's timeout is not more than INT_MAX milliseconds. The behavior with larger values is unspecified by the Single Unix Spec. It appears that BSD-derived kernels report EINVAL, although Linux does not. If waiting for longer intervals is desired, the calling code has to do somethin

[COMMITTERS] pgsql: Fix syslogger to not fail when log_rotation_age exceeds 2^31 mil

2012-11-18 Thread Tom Lane
Fix syslogger to not fail when log_rotation_age exceeds 2^31 milliseconds. We need to avoid calling WaitLatch with timeouts exceeding INT_MAX. Fortunately a simple clamp will do the trick, since no harm is done if the wait times out before it's really time to rotate the log file. Per bug #7670 (pr

[COMMITTERS] pgsql: Fix syslogger to not fail when log_rotation_age exceeds 2^31 mil

2012-11-18 Thread Tom Lane
Fix syslogger to not fail when log_rotation_age exceeds 2^31 milliseconds. We need to avoid calling WaitLatch with timeouts exceeding INT_MAX. Fortunately a simple clamp will do the trick, since no harm is done if the wait times out before it's really time to rotate the log file. Per bug #7670 (pr

[COMMITTERS] pgsql: Limit values of archive_timeout, post_auth_delay, auth_delay.mil

2012-11-18 Thread Tom Lane
Limit values of archive_timeout, post_auth_delay, auth_delay.milliseconds. The previous definitions of these GUC variables allowed them to range up to INT_MAX, but in point of fact the underlying code would suffer overflows or other errors with large values. Reduce the maximum values to something

[COMMITTERS] pgsql: Limit values of archive_timeout, post_auth_delay, auth_delay.mil

2012-11-18 Thread Tom Lane
Limit values of archive_timeout, post_auth_delay, auth_delay.milliseconds. The previous definitions of these GUC variables allowed them to range up to INT_MAX, but in point of fact the underlying code would suffer overflows or other errors with large values. Reduce the maximum values to something

[COMMITTERS] pgsql: Limit values of archive_timeout, post_auth_delay, auth_delay.mil

2012-11-18 Thread Tom Lane
Limit values of archive_timeout, post_auth_delay, auth_delay.milliseconds. The previous definitions of these GUC variables allowed them to range up to INT_MAX, but in point of fact the underlying code would suffer overflows or other errors with large values. Reduce the maximum values to something

[COMMITTERS] pgsql: Limit values of archive_timeout, post_auth_delay, auth_delay.mil

2012-11-18 Thread Tom Lane
Limit values of archive_timeout, post_auth_delay, auth_delay.milliseconds. The previous definitions of these GUC variables allowed them to range up to INT_MAX, but in point of fact the underlying code would suffer overflows or other errors with large values. Reduce the maximum values to something

[COMMITTERS] pgsql: Limit values of archive_timeout, post_auth_delay, auth_delay.mil

2012-11-18 Thread Tom Lane
Limit values of archive_timeout, post_auth_delay, auth_delay.milliseconds. The previous definitions of these GUC variables allowed them to range up to INT_MAX, but in point of fact the underlying code would suffer overflows or other errors with large values. Reduce the maximum values to something

[COMMITTERS] pgsql: Limit values of archive_timeout, post_auth_delay, auth_delay.mil

2012-11-18 Thread Tom Lane
Limit values of archive_timeout, post_auth_delay, auth_delay.milliseconds. The previous definitions of these GUC variables allowed them to range up to INT_MAX, but in point of fact the underlying code would suffer overflows or other errors with large values. Reduce the maximum values to something