Postgres Pro
Downloads
Home   >   mailing lists

Re: Investigating the reason for a very big TOAST table size - Mailing list pgsql-performance

From Daniel Farina
Subject Re: Investigating the reason for a very big TOAST table size
Date
Msg-id CAAZKuFZxdUWnYj9fQ2s7XHwQxr3ENGt_33_+GibWifPA=WM60w@mail.gmail.com
Whole thread Raw
In response to Re: Investigating the reason for a very big TOAST table size  (Liron Shiri <lirons@checkpoint.com>)
List pgsql-performance
Tree view 
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 by date:

Previous
From: Liron Shiri
Date:
Subject: Re: Investigating the reason for a very big TOAST table size
Next
From: "Albe Laurenz"
Date:
Subject: Re: Question about caching on full table scans