Re: Investigating the reason for a very big TOAST table size

Поиск
Список
Период
Сортировка
От Daniel Farina
Тема Re: Investigating the reason for a very big TOAST table size
Дата
Msg-id CAAZKuFZxdUWnYj9fQ2s7XHwQxr3ENGt_33_+GibWifPA=WM60w@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Investigating the reason for a very big TOAST table size  (Liron Shiri <lirons@checkpoint.com>)
Список pgsql-performance
On Thu, Aug 30, 2012 at 1:34 AM, Liron Shiri <lirons@checkpoint.com> wrote:
> We do not use in-database operators to modify the toasted data.
> The update operations we perform on the problematic table are in the form of
>
> UPDATE foo SET field='value' WHERE nid = to_uid(#objId#)

Ah, well, there goes that idea, although it may still be good enough
to reproduce the problem, even if it is not responsible for all
reproductions...

I guess it's time to clear some time to try.

--
fdr


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

Предыдущее
От: Liron Shiri
Дата:
Сообщение: Re: Investigating the reason for a very big TOAST table size
Следующее
От: "Albe Laurenz"
Дата:
Сообщение: Re: Question about caching on full table scans