From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tomas Vondra <tomas.vondra@2ndquadrant.com>
Cc: pgsql-performance@postgresql.org, Gunnlaugur Thor Briem <gunnlaugur@gmail.com>
Subject: Re: EXPLAIN (no ANALYZE) taking an hour for INSERT FROM SELECT
Date: Fri, 06 Mar 2015 13:36:01 -0500
Message-ID: <995.1425666961@sss.pgh.pa.us> (raw)
In-Reply-To: <54F9E179.4000804@2ndquadrant.com>
References: <CAPs+M8Kk6sGMpXN4KaANmDWXJ1F-FKwD+6szh0QmLv0HZfhY4g@mail.gmail.com>
<B6F6FD62F2624C4C9916AC0175D56D8828B82149@jenmbs01.ad.intershop.net>
<CAPs+M8JtK3EqjPp=o=CLpOCr4L_0zwmKnbr6ib2T=r+-Z4xP7Q@mail.gmail.com>
<54F8F2BB.2010402@2ndquadrant.com>
<6068.1425602694@sss.pgh.pa.us>
<54F9E179.4000804@2ndquadrant.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
Tomas Vondra <tomas.vondra@2ndquadrant.com> writes:
> On 6.3.2015 01:44, Tom Lane wrote:
>> I'm wondering about the issue addressed by commit fccebe421 ("Use
>> SnapshotDirty rather than an active snapshot to probe index
>> endpoints").
> How would fccebe421 explain the large amount of random writes (~4MB/s
> for more than an hour), reported in the initial post? And why would that
> only affect the EXPLAIN and not the bare query?
Hard to say. There's probably additional factors involved, and this
may ultimately turn out to be unrelated. But it seemed like it might
be an issue, particularly since the plan had a mergejoin with lots of
clauses ...
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
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: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, tomas.vondra@2ndquadrant.com, gunnlaugur@gmail.com
Subject: Re: EXPLAIN (no ANALYZE) taking an hour for INSERT FROM SELECT
In-Reply-To: <995.1425666961@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox