public inbox for [email protected]
help / color / mirror / Atom feedFrom: Tom Lane <[email protected]>
To: Jeff Janes <[email protected]>
Cc: [email protected]
Cc: [email protected] <[email protected]>
Subject: Re: Random slow queries
Date: Wed, 29 Jun 2016 17:44:24 -0400
Message-ID: <[email protected]> (raw)
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>
List-Unsubscribe: <mailto:[email protected]?body=unsub%20pgsql-performance>
Jeff Janes <[email protected]> writes:
> On Tue, Jun 28, 2016 at 6:24 PM, <[email protected]> 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 ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Random slow queries
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox