Re: [HACKERS] Terrible performance on wide selects

Поиск
Список
Период
Сортировка
Искать
От
Hannu Krosing
Тема
Re: [HACKERS] Terrible performance on wide selects
Дата
Msg-id
1043317847.2347.35.camel@localhost.localdomain
Ответ на
Список
Дерево обсуждения
Re: [HACKERS] Terrible performance on wide selects "Dann Corbit" <DCorbit@connx.com>
Re: [HACKERS] Terrible performance on wide selects Tom Lane <tgl@sss.pgh.pa.us>
Re: [HACKERS] Terrible performance on wide selects Hannu Krosing <hannu@tm.ee>
Re: [HACKERS] Terrible performance on wide selects Daniel Kalchev <daniel@digsys.bg>
Re: [HACKERS] Terrible performance on wide selects Tom Lane <tgl@sss.pgh.pa.us>
Re: [HACKERS] Terrible performance on wide selects Curt Sampson <cjs@cynic.net>
Tom Lane kirjutas N, 23.01.2003 kell 02:04:
> "Dann Corbit"  writes:
> > Maybe I don't really understand the problem, but it seems simple enough
> > to do it once for the whole query.
> 
> We already do cache column offsets when they are fixed.  The code that's
> the problem executes when there's a variable-width column in the table
> --- which means that all columns to its right are not at fixed offsets,
> and have to be scanned for separately in each tuple, AFAICS.

Not only varlen columns, but also NULL columns forbid knowing the
offsets beforehand.

-- 
Hannu Krosing 
В списке pgsql-performance по дате отправления
От: Hannu Krosing
Дата:
От: Hannu Krosing
Дата:
FAQ