From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Joe Van Dyk <joe(at)tanga(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Adding an additional join causes very different/slow query plan |
Date: | 2013-12-17 14:01:28 |
Message-ID: | 20131217140128.GT2543@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
* Joe Van Dyk (joe(at)tanga(dot)com) wrote:
> On Mon, Dec 16, 2013 at 4:14 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > Yup, that's what I was just about to suggest. You might want to use
> > 10 or 12 in case some of your queries are a bit more complex than
> > this one --- but don't go overboard, or you may find yourself with
> > unreasonable planning time.
> >
>
> Is there a way to measure the planning time? It's not reported in 'explain
> analyze' or 'explain analyze verbose', right?
You can just run 'explain' and that'll more-or-less get you there (turn
on \timing in psql). When reading this thread, I was thinking it might
be useful to add plan time somewhere in explain/explain analyze output
though..
Thanks,
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Kai Sellgren | 2013-12-18 02:48:10 | Optimizing a query |
Previous Message | Joe Van Dyk | 2013-12-17 00:37:03 | Re: Adding an additional join causes very different/slow query plan |