Re: BUG #13679: Planer chooses not optimal plan

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: i(dot)frolkov(at)postgrespro(dot)ru
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #13679: Planer chooses not optimal plan
Date: 2015-10-14 14:25:38
Message-ID: 27884.1444832738@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

i(dot)frolkov(at)postgrespro(dot)ru writes:
> See two explain analyze below:

I see no particular bug here. Given the speeds you're getting out of that
inner indexscan, you need to increase effective_cache_size and/or reduce
random_page_cost to reflect actual execution costs on your hardware.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Aaron C. de Bruyn 2015-10-14 15:37:19 Re: BUG #13637: ~2 GB psql import fails with out of memory error on machine with 64 GB RAM
Previous Message John Pruitt 2015-10-14 14:24:39 Re: BUG #13670: DST discrepancy between age() and subtraction for timestamptz arguments