Re: Statement timeout behavior in extended queries

From: 'Andres Freund' <andres(at)anarazel(dot)de>
To: "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>
Cc: Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>, "david(at)fetter(dot)org" <david(at)fetter(dot)org>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Statement timeout behavior in extended queries
Date: 2017-04-04 23:56:26
Message-ID: 20170404235626.6pr6osxzmj32c6th@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2017-04-04 23:52:28 +0000, Tsunakawa, Takayuki wrote:
> From: Andres Freund [mailto:andres(at)anarazel(dot)de]
> > Looks to me like npgsql doesn't do that either. None of libpq, pgjdbs and
> > npgsql doing it seems like some evidence that it's ok.
>
> And psqlODBC now uses always libpq.
>
> Now time for final decision?

I'll send an updated patch in a bit, and then will wait till tomorrow to
push. Giving others a chance to chime in seems fair.

- Andres

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Craig Ringer 2017-04-05 00:00:28 Re: Faster methods for getting SPI results (460% improvement)
Previous Message Tsunakawa, Takayuki 2017-04-04 23:52:28 Re: Statement timeout behavior in extended queries