Permalink
Commits on Jul 13, 2011
  1. fixed an issue regarding defining global variables in C header files:…

    … we should have defined rds_rough_col_type_t as a type rather than a global variable. thanks @姜大炮.
    agentzh committed Jul 13, 2011
Commits on Jun 21, 2011
  1. Always return first (and only) value for "postgres_output value".

    This is second part of the "write proper SQL queries" campaign. Queries
    that return more than one value will result in "500 Internal Server Error"
    response.
    PiotrSikora committed Jun 21, 2011
  2. Replace "postgres_output row <row>" with "postgres_output text".

    This is more general approach, which forces writing proper SQL queries
    instead of filtering results on the nginx side and allows for sending
    output from multiple rows to end-users.
    
    Discussed with Silly Sad.
    PiotrSikora committed Jun 21, 2011
Commits on Jun 17, 2011
  1. Improve library discovery process by using PostgreSQL's pg_config.

    Based on patch from Silly Sad.
    PiotrSikora committed Jun 17, 2011
  2. Don't set last_buf=1 (duplicated last chunk issue).

    Because ngx_http_upstream_finalize_request sends NGX_HTTP_LAST,
    having last_buf=1 in our module meant that last two chains always
    had last_buf=1, which resulted in duplicated last chunk sent for
    HTTP/1.1 requests. This pretty much killed keep-alived requests.
    
    Reported by Silly Sad, diagnosed by Maxim Dounin.
    
    Same issue was independently diagnosed and fixed in ngx_drizzle
    by Yichun Zhang (agentzh) few days ago.
    PiotrSikora committed Jun 17, 2011
Commits on May 11, 2011
  1. updated .gitignore a bit.

    agentzh committed May 11, 2011
Commits on Feb 18, 2011
  1. removed the hand-written << "in upstream \"t.shV\"", &pgdt->name >> p…

    …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.
    agentzh committed Feb 18, 2011
  2. fixed a bug in the connection pool: we should copy over the "name" an…

    …d "sockaddr" fields instead of passing pointers around.
    agentzh committed Feb 18, 2011
Commits on Feb 17, 2011
  1. fixed a minor bug in the connection pool: we should resume the "name"…

    …, "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.
    agentzh committed Feb 17, 2011
Commits on Jan 13, 2011
  1. Use PQescapeLiteral() to detect PostgreSQL 9.0.

    Calling PQconnectStartParams(NULL, *, *) results in SIGSEGV.
    PiotrSikora committed Jan 13, 2011
Commits on Jan 4, 2011
Commits on Dec 23, 2010
  1. Revert fixed jump on uninitialized value.

    The problem is that this value shouldn't be used in the first place
    (see next commit).
    
    This reverts commit 1ed9f15.
    PiotrSikora committed Dec 23, 2010
  2. Revert "postgres_binary_mode".

    This is great feature, but the way it hooks into configuration must
    be rewritten (as discussed with Yichun on the IRC).
    
    This reverts commit 4187c57.
    PiotrSikora committed Dec 23, 2010
Commits on Dec 22, 2010
  1. Revert fix backported from ngx_drizzle.

    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.
    PiotrSikora committed Dec 22, 2010
  2. Publish roadmap.

    PiotrSikora committed Dec 22, 2010
Commits on Nov 4, 2010
  1. backported a patch from ngx_drizzle: fixed a bug: we did not initialize

    r->upstream->peer.name in the get_peer function which caused error
    messages lacking upstream peer names and ports.
    agentzh committed Nov 4, 2010
Commits on Nov 3, 2010
Commits on Nov 2, 2010