Re: Simply join in PostrgeSQL takes too long
От
Manfred Koizar
Тема
Re: Simply join in PostrgeSQL takes too long
Дата
Msg-id
lkd29018sbqg8bhcr3dabfjf6u6jckib3t@email.aon.at
Ответ на
Re: Simply join in PostrgeSQL takes too long (Rod Taylor)
Список
Дерево обсуждения
Simply join in PostrgeSQL takes too long Vitaly Belman <vitalib@012.net.il>
Re: Simply join in PostrgeSQL takes too long "Atesz" <atesz@ritek.hu>
Re: Simply join in PostrgeSQL takes too long Rod Taylor <pg@rbt.ca>
Re: Simply join in PostrgeSQL takes too long Manfred Koizar <mkoi-pg@aon.at>
Re: Simply join in PostrgeSQL takes too long Rod Taylor <pg@rbt.ca>
Re: Simply join in PostrgeSQL takes too long Manfred Koizar <mkoi-pg@aon.at>
Re: Simply join in PostrgeSQL takes too long Rod Taylor <pg@rbt.ca>
Re: Simply join in PostrgeSQL takes too long Manfred Koizar <mkoi-pg@aon.at>
Re: Simply join in PostrgeSQL takes too long Vitaly Belman <vitalib@012.net.il>
Re: Simply join in PostrgeSQL takes too long Josh Berkus <josh@agliodbs.com>
Re: Simply join in PostrgeSQL takes too long Josh Berkus <josh@agliodbs.com>
Re: Simply join in PostrgeSQL takes too long Nick Barr <nicky@chuckie.co.uk>
On Wed, 28 Apr 2004 08:23:35 -0400, Rod Taylor wrote: >The below plpgsql forces the kind of algorithm we wish the planner could >choose. It should be fairly quick irregardless of dataset. That reminds me of hash aggregation. So here's another idea for Vitaly: SELECT book_id FROM ... WHERE ... GROUP BY book_id LIMIT ... Servus Manfred
В списке pgsql-performance по дате отправления
