Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Commits on Jul 4, 2015
  1. @agentzh

    feature: fixed compilation errors with nginx 1.9.1+. thanks Vadim A. …

    agentzh authored
    …Misbakh-Soloviov for the original patch in #38.
Commits on Jun 16, 2015
  1. @agentzh
Commits on Apr 2, 2015
  1. @agentzh
Commits on Sep 17, 2014
  1. @agentzh

    bugfix: fixed compilation error with nginx 1.7.5+ because nginx 1.7.5…

    agentzh authored
    …+ changes the API in the events subsystem.
Commits on Aug 18, 2014
  1. @agentzh
Commits on Aug 1, 2014
  1. @agentzh

    bugfix: segmentation fault might happen in ngx_destroy_pool when debu…

    agentzh authored
    …g logging was enabled in the nginx build. thanks buddy-ekb for the report in #21.
Commits on Jul 31, 2013
  1. @agentzh

    bugfix: compilation error happened with nginx 1.5.3+ because nginx ch…

    agentzh authored
    …anges the ngx_sock_ntop API. thanks an0ma1ia for the report in #19.
Commits on Aug 17, 2012
  1. @agentzh

    removed the useless http-cache related code from ngx_postgres_upstrea…

    agentzh authored
    …m_finalize_request to suppress clang warnings.
  2. @agentzh

    bugfix: the "open socket #n left in connection" alerts would appear i…

    agentzh authored
    …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.
Commits on Jun 21, 2012
  1. @agentzh

    bugfix: memory leak might happen if nginx 1.1.14+ is used *and* (at l…

    agentzh authored
    …east) libpq fails to connect to the remote database.
Commits on Feb 2, 2012
  1. @agentzh
Commits on Dec 27, 2011
  1. @PiotrSikora

    Remove trailing whitespaces.

    PiotrSikora authored
    Change-Id: I4c63b363cc922521eb2e48e93d1db0a4e4c0f105
    Signed-off-by: Piotr Sikora <piotr.sikora@frickle.com>
  2. @PiotrSikora

    Add nginx-style debug logging.

    PiotrSikora authored
    Based on patch from Yichun Zhang (agentzh).
    
    Change-Id: If2094a3a300500b1a6710e59d148e83abf3b6da4
    Signed-off-by: Piotr Sikora <piotr.sikora@frickle.com>
Commits on Dec 23, 2011
  1. @PiotrSikora

    Make sure that the write event really occured before re-polling.

    PiotrSikora authored
    The "re-polling" hack to work-around the case in which both:
    read and write events occured within the same event processing
    call was being used for any CONNECTION_MADE status, without
    checking if the write really occured.
    
    Based on patch from Yichun Zhang (agentzh).
    
    Change-Id: Ia8310a109baf639d1c5c3c766d2298c3610e6d47
    Signed-off-by: Piotr Sikora <piotr.sikora@frickle.com>
  2. @PiotrSikora

    Fix compatibility with poll, select and /dev/poll event models.

    PiotrSikora authored
    Reported by Yichun Zhang (agentzh).
    
    Change-Id: I9411e72ccfdbb0d974a92b6cba569dc15254ed3d
    Signed-off-by: Piotr Sikora <piotr.sikora@frickle.com>
Commits on Nov 10, 2011
  1. @PiotrSikora

    Fix compatibility with PostgreSQL 9.x: rows affected.

    PiotrSikora authored
    Starting with PostgreSQL 9.0, libpq's PQcmdTuples() returns row count
    for SELECT queries (previously it returned empty string).
    
    Because we're using this value to detect number of changed rows,
    both: "postgres_rewrite" directive and "$postgres_affected" variable
    were working incorrectly.
    
    Reported by Yichun Zhang (agentzh).
  2. @agentzh @PiotrSikora

    bugfix: now we log an error message when the postgres_pass target is …

    agentzh authored PiotrSikora committed
    …not found at all and returns 500 in this case instead of returning empty response.
  3. @PiotrSikora

    Allow global definition of DDEBUG.

    PiotrSikora authored
    From Yichun Zhang (agentzh).
  4. @PiotrSikora

    Fix compatibility with nginx-1.1.4+.

    PiotrSikora authored
    Partly from Yichun Zhang (agentzh).
Commits on Jul 13, 2011
  1. @agentzh

    fixed an issue regarding defining global variables in C header files:…

    agentzh authored
    … we should have defined rds_rough_col_type_t as a type rather than a global variable. thanks @姜大炮.
Commits on Jun 21, 2011
  1. @PiotrSikora

    Always return first (and only) value for "postgres_output value".

    PiotrSikora authored
    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.
  2. @PiotrSikora

    Replace "postgres_output row <row>" with "postgres_output text".

    PiotrSikora authored
    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.
  3. @PiotrSikora
Commits on Jun 17, 2011
  1. @PiotrSikora

    Don't set last_buf=1 (duplicated last chunk issue).

    PiotrSikora authored
    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.
Commits on Feb 18, 2011
  1. @agentzh

    removed the hand-written << "in upstream \"t.shV\"", &pgdt->name >> p…

    agentzh authored
    …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.
  2. @agentzh

    fixed a bug in the connection pool: we should copy over the "name" an…

    agentzh authored
    …d "sockaddr" fields instead of passing pointers around.
Commits on Feb 17, 2011
  1. @agentzh

    fixed a minor bug in the connection pool: we should resume the "name"…

    agentzh authored
    …, "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.
Commits on Dec 23, 2010
  1. @PiotrSikora
  2. @PiotrSikora

    Revert fixed jump on uninitialized value.

    PiotrSikora authored
    The problem is that this value shouldn't be used in the first place
    (see next commit).
    
    This reverts commit 1ed9f15.
  3. @PiotrSikora
  4. @PiotrSikora
  5. @PiotrSikora

    Revert "postgres_binary_mode".

    PiotrSikora authored
    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.
Commits on Dec 22, 2010
  1. @PiotrSikora
  2. @PiotrSikora

    Revert fix backported from ngx_drizzle.

    PiotrSikora authored
    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.
Commits on Nov 4, 2010
  1. @agentzh

    backported a patch from ngx_drizzle: fixed a bug: we did not initialize

    agentzh authored
    r->upstream->peer.name in the get_peer function which caused error
    messages lacking upstream peer names and ports.
Something went wrong with that request. Please try again.