pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Pavel Rotek <pavel.rotek@gmail.com>
To: pgsql-performance@postgresql.org
Subject: Re: Toast space grows
Date: Fri, 7 Mar 2008 10:29:33 +0100
Message-ID: <3556c08c0803070129y6ffabf32i1c8bae445ec460e0@mail.gmail.com> (raw)
In-Reply-To: <47D10722.4080508@archonet.com>
References: <3556c08c0803070035p6d8b4aa8m6318f54728f61022@mail.gmail.com>
	<47D10722.4080508@archonet.com>

we just restored it to free 70G :-(

There are inserts and few updates (but what do you mean with update??
committed update??, because there are many updates of the log attribute in
trasaction, we do periodical flush during transaction), 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.

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
>

view thread (15+ messages)  latest in thread

Message-ID: <3556c08c0803070129y6ffabf32i1c8bae445ec460e0@mail.gmail.com>
Permalink:  ../3556c08c0803070129y6ffabf32i1c8bae445ec460e0@mail.gmail.com/
Also on:    postgresql.org/message-id/3556c08c0803070129y6ffabf32i1c8bae445ec460e0@mail.gmail.com

 · 

reply

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: pavel.rotek@gmail.com
  Subject: Re: Toast space grows
  In-Reply-To: <3556c08c0803070129y6ffabf32i1c8bae445ec460e0@mail.gmail.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