| From: | henk de wit <henk53602(at)hotmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Query with limit goes from few ms to hours |
| Date: | 2012-10-15 17:50:18 |
| Message-ID: | COL104-W36CB0D0DE2DB88A5D64459F5710@phx.gbl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Hi,
> henk de wit <henk53602(at)hotmail(dot)com> writes:
> > For some reason the mailinglist software seems to block the email as soon as the planner details are in it, so I pasted those on pastebin.com: http://pastebin.com/T5JTwh5T
>
> You need a less horrid estimate for the join size. Possibly an ANALYZE
> on the parent table (stream_store) would help.
Well, what do you know! That did work indeed. Immediately after the ANALYZE on that parent table (taking only a few seconds) a fast plan was created and the query executed in ms again. Silly me, I should have tried that earlier.
Thanks!
Kind regards
| From | Date | Subject | |
|---|---|---|---|
| Next Message | houmanb | 2012-10-15 20:59:16 | SELECT AND AGG huge tables |
| Previous Message | Pedro Jiménez | 2012-10-15 17:44:46 | limit order by performance issue |