pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Craig Ringer <craig@postnewspapers.com.au>
To: John Williams <jwilliams@42nddesign.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Set of related slow queries
Date: Wed, 08 Jun 2011 17:20:46 +0800
Message-ID: <4DEF3EEE.1080203@postnewspapers.com.au> (raw)
In-Reply-To: <BANLkTik-SdA2+-VKgBYhOpfNTXM0mgWEig@mail.gmail.com>
References: <BANLkTik-SdA2+-VKgBYhOpfNTXM0mgWEig@mail.gmail.com>

On 8/06/2011 10:58 AM, John Williams wrote:

>                 ->   Bitmap Heap Scan on logparser_entry
> (cost=4119.06..21520.55 rows=68787 width=8) (actual
> time=107.032..444.864 rows=16168 loops=1)
>                       Recheck Cond: ((event_type)::text = ANY
> ('{Attack,"DoT Tick","Critical Attack"}'::text[]))
>                       Filter: ((((target_relation)::text<>  ALL
> ('{Other,N/A}'::text[])) OR (NOT (target_relation IS NOT NULL))) AND
> (log_id = 2))
>                       ->   Bitmap Index Scan on
> logparser_entry_event_type_like  (cost=0.00..4101.86 rows=217733
> width=0) (actual time=46.392..46.392 rows=237151 loops=1)
>                             Index Cond: ((event_type)::text = ANY
> ('{Attack,"DoT Tick","Critical Attack"}'::text[]))
>                 ->   Hash  (cost=196.49..196.49 rows=9749 width=23)
> (actual time=19.606..19.606 rows=9749 loops=1)

Thanks for including explain analyze output.

Is there any chance you can pop the full explains (not just excerpts) in 
here:

http://explain.depesz.com/

?

Big query plans tend to get mangled into unreadable garbage by mail 
clients, unfortunately.

-- 
Craig Ringer

Tech-related writing at http://soapyfrogs.blogspot.com/



view thread (7+ messages)  latest in thread

Message-ID: <4DEF3EEE.1080203@postnewspapers.com.au>
Permalink:  ../4DEF3EEE.1080203@postnewspapers.com.au/
Also on:    postgresql.org/message-id/4DEF3EEE.1080203@postnewspapers.com.au

 · 

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: pgsql-performance@postgresql.org
  Cc: craig@postnewspapers.com.au, jwilliams@42nddesign.com
  Subject: Re: Set of related slow queries
  In-Reply-To: <4DEF3EEE.1080203@postnewspapers.com.au>

* 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