From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jeff Janes <jeff.janes@gmail.com>
cc: devel.brain99@xoxy.net,
        "pgsql-performance@postgresql.org" <pgsql-performance@postgresql.org>
Subject: Re: Random slow queries
In-reply-to: 
 <CAMkU=1y9f7-STVh=rFweXkpnNXBo8C5AmMwn09qRikuAU-eieA@mail.gmail.com>
References: 
 <CACjsgDm+n0s=5cMwGF7nRMXS8fX6CF9t1HsOr_M2iejpxKgS1A@mail.gmail.com>
 <CAMkU=1y9f7-STVh=rFweXkpnNXBo8C5AmMwn09qRikuAU-eieA@mail.gmail.com>
Comments: In-reply-to Jeff Janes <jeff.janes@gmail.com>
	message dated "Wed, 29 Jun 2016 14:30:35 -0700"
Date: Wed, 29 Jun 2016 17:44:24 -0400
Message-ID: <9890.1467236664@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-performance-owner@postgresql.org

Jeff Janes <jeff.janes@gmail.com> writes:
> On Tue, Jun 28, 2016 at 6:24 PM,  <devel.brain99@xoxy.net> wrote:
>> PostgreSQL 9.3.4, compiled by Visual C++ build 1600, 64-bit

> The current minor version of that branch is 9.3.13, so you are 9 bug
> fix releases behind.

Definitely a fair complaint.

> I don't know if this matters, because I see that my first guess of
> your problem was fixed in commit 4162a55c77cbb54acb4ac442e, which was
> already included in 9.3.4.

That commit could have helped if the problem were simply slow planning.
But I do not see how it explains a *consistent* 122-second delay.
That sounds very much like a timeout expiring someplace, and I have
no idea where.

			regards, tom lane


-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance