Re: TOAST usage setting

Поиск
Список
Период
Сортировка
От Gregory Stark
Тема Re: TOAST usage setting
Дата
Msg-id 87d50hicyt.fsf@oxford.xeocode.com
обсуждение исходный текст
Ответ на Re: TOAST usage setting  (Gregory Stark <stark@enterprisedb.com>)
Ответы Re: TOAST usage setting  (Bruce Momjian <bruce@momjian.us>)
Список pgsql-hackers
"Gregory Stark" <stark@enterprisedb.com> writes:

> "Bruce Momjian" <bruce@momjian.us> writes:
>
>> shared_buffers again was 32MB so all the data was in memory.
>
> The case where all the data is in memory is simply not interesting. The cost
> of TOAST is the random access seeks it causes. You seem to be intentionally
> avoiding testing the precise thing we're interested in.

Also, something's not right with these results. 100,000 tuples --even if all
they contain is a toast pointer-- won't fit on a single page. And the toast
tables should vary in size depending on how many toast chunks are created.

--  Gregory Stark EnterpriseDB          http://www.enterprisedb.com



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

Предыдущее
От: Gregory Stark
Дата:
Сообщение: Re: TOAST usage setting
Следующее
От: Heikki Linnakangas
Дата:
Сообщение: Re: [COMMITTERS] pgsql: Make large sequential scans and VACUUMs work in a limited-size