Re: BUG #14891: Old cancel request presented by pgbouncer honored after skipping a query.

From: Skarsol <postgresql(at)skarsol(dot)com>
To: Greg Stark <stark(at)mit(dot)edu>
Cc: PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org>, gsstark(at)gmail(dot)com
Subject: Re: BUG #14891: Old cancel request presented by pgbouncer honored after skipping a query.
Date: 2017-12-19 16:52:09
Message-ID: 42e9e516a915015440c9b0b28239fa82@wurm.cx
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 2017-12-19 10:43, Greg Stark wrote:
> If I understand the bug report correctly you have two layers of
> pgbouncer and it's only the second layer that is introducing these
> latencies? I wonder if that should help point out why these latencies
> are happening but I don't have any immediate ideas.

To clarify, we also see the issue in cases where there is only one PGB
between the client and the database.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Andres Freund 2017-12-19 18:31:14 vacuum vs heap_update_tuple() and multixactids
Previous Message Greg Stark 2017-12-19 16:43:46 Re: BUG #14891: Old cancel request presented by pgbouncer honored after skipping a query.