Re: 8.3devel slower than 8.2 under read-only load

Поиск
Список
Период
Сортировка
От Gregory Stark
Тема Re: 8.3devel slower than 8.2 under read-only load
Дата
Msg-id 871wadiwgu.fsf@oxford.xeocode.com
обсуждение исходный текст
Ответ на Re: 8.3devel slower than 8.2 under read-only load  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: 8.3devel slower than 8.2 under read-only load  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
"Tom Lane" <tgl@sss.pgh.pa.us> writes:

> But since your columns are varchar, which doesn't have any operators of its
> own, we have to go through oper_select_candidate()

I wonder whether at some point we shouldn't just eliminate this distinction
entirely. Just make "text" and "varchar" the same type and spell it "text"
when there's no typmod length restriction and "varchar(x)" when there is.

> 1. Datatype bloat: there are 58 "=" operators in pg_operator today,
> versus 54 at the beginning of the year.  That's 7% more work right
> there to sort through the additional operators.

That's particularly scary because it means that databases which load piles of
contrib modules have that much more of an effect here. Some contrib modules
create a *lot* of operators.

--  Gregory Stark EnterpriseDB          http://www.enterprisedb.com Ask me about EnterpriseDB's RemoteDBA services!


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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: quote_literal(integer) does not exist
Следующее
От: Tom Lane
Дата:
Сообщение: Re: 8.3devel slower than 8.2 under read-only load