Re: Confronting the maximum column limitation

Поиск
Список
Период
Сортировка
От Decibel!
Тема Re: Confronting the maximum column limitation
Дата
Msg-id E8EF2CA8-D0C7-44DD-A23D-B5BF36B0446D@decibel.org
обсуждение исходный текст
Ответ на Confronting the maximum column limitation  (Jeff Gentry <jgentry@jimmy.harvard.edu>)
Ответы Re: Confronting the maximum column limitation  ("Scott Marlowe" <scott.marlowe@gmail.com>)
Список pgsql-general
On Aug 12, 2008, at 3:15 PM, Jeff Gentry wrote:
> So I've seen the header file where the 1600 column limit is defined


IIRC, that limit is directly related to block size in the header, so
one possible fix is to increase block size. AFAIK anything up to 64K
blocks should be safe.

BTW, keep in mind that if you're storing anything that's a varlena
(anything that's variable length, including NUMBER) where you have
that many columns, every single varlena is going to end up toasted.
That's bound to have a *serious* performance impact.
--
Decibel!, aka Jim C. Nasby, Database Architect  decibel@decibel.org
Give your computer some brain candy! www.distributed.net Team #1828



Вложения

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

Предыдущее
От: "Ian Harding"
Дата:
Сообщение: Re: How to tell if a trigger is disabled
Следующее
От: Decibel!
Дата:
Сообщение: Re: Changing between ORDER BY DESC and ORDER BY ASC