Re: poor performing plan from analyze vs. fast default plan pre-analyze on new database - Mailing list pgsql-performance

From Grzegorz Jaśkiewicz
Subject Re: poor performing plan from analyze vs. fast default plan pre-analyze on new database
Date
Msg-id 2f4958ff0906030907g1d6e969dq61956d7e192d5dfe@mail.gmail.com
Whole thread Raw
In response to poor performing plan from analyze vs. fast default plan pre-analyze on new database  (Davin Potts <davin@appliomics.com>)
List pgsql-performance
Postgresql isn't very efficient with subselects like that,
try:
explain select c.id from content c LEFT JOIN (select min(id) AS id
from content group by hash) cg ON cg.id=c.id WHERE cg.id is null;

pgsql-performance by date:

Previous
From: Davin Potts
Date:
Subject: poor performing plan from analyze vs. fast default plan pre-analyze on new database
Next
From: Tom Lane
Date:
Subject: Re: poor performing plan from analyze vs. fast default plan pre-analyze on new database