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

From: Daniel Farina <daniel(at)heroku(dot)com>
To: Liron Shiri <lirons(at)checkpoint(dot)com>
Cc: "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Investigating the reason for a very big TOAST table size
Date: 2012-08-30 08:39:30
Message-ID: CAAZKuFZxdUWnYj9fQ2s7XHwQxr3ENGt_33_+GibWifPA=WM60w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Thu, Aug 30, 2012 at 1:34 AM, Liron Shiri <lirons(at)checkpoint(dot)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

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Albe Laurenz 2012-08-30 09:31:24 Re: Question about caching on full table scans
Previous Message Liron Shiri 2012-08-30 08:34:48 Re: Investigating the reason for a very big TOAST table size