Re: Re: 500rows = 1min/2.5k rows=20min/6K rows 2 hours and still running

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Re: 500rows = 1min/2.5k rows=20min/6K rows 2 hours and still running
Дата
Msg-id 22159.1189608076@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: Re: 500rows = 1min/2.5k rows=20min/6K rows 2 hours and still running  (El-Lotso <el.lotso@gmail.com>)
Ответы Re: Re: 500rows = 1min/2.5k rows=20min/6K rows 2 hours and still running  (El-Lotso <el.lotso@gmail.com>)
Список pgsql-performance
El-Lotso <el.lotso@gmail.com> writes:
> I'm really at my wits end here.

Try to merge the multiple join keys into one, somehow.  I'm not sure why
the planner is overestimating the selectivity of the combined join
conditions, but that's basically where your problem is coming from.

A truly brute-force solution would be "set enable_nestloop = off"
but this is likely to screw performance for other queries.

            regards, tom lane

В списке pgsql-performance по дате отправления:

Предыдущее
От: Nis Jørgensen
Дата:
Сообщение: Re: 500rows = 1min/2.5k rows=20min/6K rows 2 hours and still running
Следующее
От: Rafael Barrera Oro
Дата:
Сообщение: Re: random_page_costs - are defaults of 4.0 realistic for SCSI RAID 1