…+ changes the API in the events subsystem.
…g logging was enabled in the nginx build. thanks buddy-ekb for the report in #21.
…anges the ngx_sock_ntop API. thanks an0ma1ia for the report in #19.
…m_finalize_request to suppress clang warnings.
…n the nginx error log file when the pg connection pool was used and the worker process was shutting down. this issue could be captured by running t/sanity.t with the environment TEST_NGINX_USE_HUP=1.
…east) libpq fails to connect to the remote database.
…not found at all and returns 500 in this case instead of returning empty response.
… we should have defined rds_rough_col_type_t as a type rather than a global variable. thanks @姜大炮.
…art from most of the ngx_log_error calls in ngx_postgres_keepalive.c because they are duplicate with the << upstream: "postgres://ip.add.re.ss:port" >> part automatically generated by the ngx_http_log_error_handler function in the nginx core.
…d "sockaddr" fields instead of passing pointers around.
…, "sockaddr", and "socklen" fields for the connection from the pool such that we can get more detailed error log messages with the "upstream: postgres://ip.add.re.ss:port" bit.