Re: Increasing work_mem and shared_buffers on Postgres 9.2 significantly slows down queries

From: Andres Freund <andres(at)2ndquadrant(dot)com>
To: Petr Praus <petr(at)praus(dot)net>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Increasing work_mem and shared_buffers on Postgres 9.2 significantly slows down queries
Date: 2012-11-09 17:53:45
Message-ID: 20121109175345.GA16999@awork2.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On 2012-10-30 14:08:56 -0500, Petr Praus wrote:
> select count(*) from contest c
> left outer join contestparticipant cp on c.id=cp.contestId
> left outer join teammember tm on tm.contestparticipantid=cp.id
> left outer join staffmember sm on cp.id=sm.contestparticipantid
> left outer join person p on p.id=cp.personid
> left outer join personinfo pi on pi.id=cp.personinfoid
> where pi.lastname like '%b%' or pi.firstname like '%a%';

Btw, not really related to the question, but the way you use left joins
here doesn't really make sense and does lead to inferior plans.
As you restrict on 'pi', the rightmost table in a chain of left joins,
there is no point in all those left joins. I would guess the overall
plan is better if use straight joins.

Greetings,

Andres Freund

--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Jeff Janes 2012-11-09 20:47:37 Re: [HACKERS] pg_dump and thousands of schemas
Previous Message Merlin Moncure 2012-11-09 15:04:20 Re: Thousands databases or schemas