On Thu, Aug 30, 2012 at 1:34 AM, Liron Shiri 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, althoug
ay, August 30, 2012 11:11 AM
To: Liron Shiri
Cc: pgsql-performance@postgresql.org
Subject: Re: [PERFORM] Investigating the reason for a very big TOAST table size
On Mon, Aug 27, 2012 at 11:24 PM, Liron Shiri wrote:
> There were no "hot standby" configuration, but the DB has s
On Mon, Aug 27, 2012 at 11:24 PM, Liron Shiri wrote:
> There were no "hot standby" configuration, but the DB has start grow fast
> after restoring from a base backup as described in
> http://www.postgresql.org/docs/8.3/static/continuous-archiving.html#BACKUP-BASE-BACKUP
I'm trying to confirm a
On Tue, Aug 28, 2012 at 1:57 AM, Daniel Farina wrote:
> My database has taken many days (over a week) to stabilize. I was
> about to write that it never stops growing (we'd eventually have to
> VACUUM FULL or do a column rotation), but that is not true. This
> graph is a bit spotty for unrelated
On Mon, Aug 27, 2012 at 11:24 PM, Liron Shiri wrote:
> There were no "hot standby" configuration, but the DB has start grow fast
> after restoring from a base backup as described in
> http://www.postgresql.org/docs/8.3/static/continuous-archiving.html#BACKUP-BASE-BACKUP
Very interesting. That
To: Liron Shiri
Cc: pgsql-performance@postgresql.org
Subject: Re: [PERFORM] Investigating the reason for a very big TOAST table size
On Sun, Aug 26, 2012 at 5:46 AM, Liron Shiri wrote:
> Hi,
>
>
>
> We have a table which its TOAST table size is 66 GB, and we believe
> should be sm
On Sun, Aug 26, 2012 at 5:46 AM, Liron Shiri wrote:
> Hi,
>
>
>
> We have a table which its TOAST table size is 66 GB, and we believe should
> be smaller.
>
> The table size is 472 kb. And the table has 4 columns that only one of them
> should be toasted.
>
>
>
> The table has only 8 dead tuples,
Hi,
We have a table which its TOAST table size is 66 GB, and we believe should be
smaller.
The table size is 472 kb. And the table has 4 columns that only one of them
should be toasted.
The table has only 8 dead tuples, so apparently this is not the problem.
This table contains a column with b
From: Liron Shiri
Sent: Sunday, August 26, 2012 3:47 PM
To: 'pgsql-performance@postgresql.org'
Subject: Investigating the reason for a very big TOAST table size
Importance: High
Hi,
We have a table which its TOAST table size is 66 GB, and we believe should be
smaller.
The table size is 472 kb.
