From: Bill Moran <wmoran@collaborativefusion.com>
To: Pavel Rotek <pavel.rotek@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Toast space grows
Date: Fri, 7 Mar 2008 06:53:14 -0500
Message-ID: <20080307065314.1248665b.wmoran@collaborativefusion.com> (raw)
In-Reply-To: <3556c08c0803070129y6ffabf32i1c8bae445ec460e0@mail.gmail.com>
References: <3556c08c0803070035p6d8b4aa8m6318f54728f61022@mail.gmail.com>
<47D10722.4080508@archonet.com>
<3556c08c0803070129y6ffabf32i1c8bae445ec460e0@mail.gmail.com>
In response to "Pavel Rotek" <pavel.rotek@gmail.com>:
>
> There are inserts and few updates (but what do you mean with update??
He means adding or changing data in the table.
> committed update??, because there are many updates of the log attribute in
> trasaction, we do periodical flush during transaction)
Are you saying you have long-running transactions? How long does a
single transaction take?
Transactions prevent vacuum from being able to clean up. Long running
transactions tend to render vacuum ineffective.
>, sum takes
> approximately 1,2G, and i mean vacuum full (but there is no lock on the
> table when running vacuum full). I haven't try plain vacuum.
Don't do vacuum full on this table. Do frequent vacuums. The table will
bloat some, but not 10x the required size, once you find a reasonable
frequency for vacuums. You might find it practical to manually vacuum
this table from your application after insert and update operations.
>
> 2008/3/7, Richard Huxton <dev@archonet.com>:
> >
> > Pavel Rotek wrote:
> > > Hello,
> > >
> > > i have problem with following table...
> > >
> > > create table dataaction (
> > > id INT4 not null,
> > > log text,
> > > primary key (id)
> > > );
> > >
> > > It is the table for storing results of long running jobs. The log
> > attribute
> > > takes approximately 5MB for one row (there is about 300 rows). My
> > problem
> > > is, that table dataaction takes after restoring about 1,5G, but in few
> > days
> > > grows to 79G(Toast space)...
> >
> >
> > 1. What is happening with this table - just inserts, lots of updates?
> >
> > 2. What does SELECT sum(length(log)) FROM dataaction; show?
> >
> >
> > > Vacuum on the table doesn't finish.
> >
> >
> > A plain vacuum doesn't finish, or vacuum full doesn't finish?
> >
> >
> > --
> > Richard Huxton
> > Archonet Ltd
> >
>
--
Bill Moran
Collaborative Fusion Inc.
http://people.collaborativefusion.com/~wmoran/
wmoran@collaborativefusion.com
Phone: 412-422-3463x4023
****************************************************************
IMPORTANT: This message contains confidential information and is
intended only for the individual named. If the reader of this
message is not an intended recipient (or the individual
responsible for the delivery of this message to an intended
recipient), please be advised that any re-use, dissemination,
distribution or copying of this message is prohibited. Please
notify the sender immediately by e-mail if you have received
this e-mail by mistake and delete this e-mail from your system.
E-mail transmission cannot be guaranteed to be secure or
error-free as information could be intercepted, corrupted, lost,
destroyed, arrive late or incomplete, or contain viruses. The
sender therefore does not accept liability for any errors or
omissions in the contents of this message, which arise as a
result of e-mail transmission.
****************************************************************
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: wmoran@collaborativefusion.com, pavel.rotek@gmail.com
Subject: Re: Toast space grows
In-Reply-To: <20080307065314.1248665b.wmoran@collaborativefusion.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox