I've just tested each case and there is no such bug in ngx_postgres, each error.log entry contains correct upstream peer name. I'll re-add "pc->name = &peer->name;" in case nginx or 3rd-party modules will ever use it, but "pc->name" isn't used by ngx_postgres. This reverts commit 8126a4f.
r->upstream->peer.name in the get_peer function which caused error messages lacking upstream peer names and ports.
…ould always initialize pglcf->output_value->required.
It is now possible to: - escape variable in-place, - escape both anonymous and named regex captures, - safely re-use same $escaped variable name in different locations, - concatenate multiple variables/strings and escape them into single variable. All this comes at the price of not being able to tell the difference between empty string and non-existing value, which means that starting with this commit all empty strings will be escaped to NULL value. This behavior can be disabled by prefixing unescaped value with '=' sign.
… "postgres_rewrite" directive.