From: | "Jeffrey W(dot) Baker" <jwb(at)saturn5(dot)com> |
---|---|
To: | John Gray <jgray(at)azuli(dot)co(dot)uk> |
Cc: | Postgres general mailing list <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pg_toast table growth out of control |
Date: | 2002-03-11 20:23:54 |
Message-ID: | 1015878235.31858.17.camel@heat |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, 2002-03-11 at 12:18, John Gray wrote:
> On Mon, 2002-03-11 at 19:00, Jeffrey W. Baker wrote:
> > (resent -- mailing lists seem horked up today)
> >
> > I have a pg_toast table that is using up my entire storage device. When
> > I vacuum the database, it does not get smaller. This is driving me
> > crazy, since I have to dump and reload the data to shrink the database.
> >
>
> Are you using VACUUM FULL at all? AIUI, the current VACUUM will
> generally not truncate tables -in this respect, the TOAST table is like
> any other.
>
> I would suggest running VACUUM FULL VERBOSE resp_body; and see whether
> you get any different message. (this gets an exclusive lock on the
> table, so it will block operations on resp_body while it operates).
That isn't the problem ... the rest of my tables get truncated normally
but only this one which contains long objects grows.
In any case VACUUM FULL takes ages. pg_dump + pg_restore is actually
faster.
-jwb
From | Date | Subject | |
---|---|---|---|
Next Message | Oliver Elphick | 2002-03-11 20:33:35 | Re: Can't get ODBC from Windows to Linux/Postgres to work |
Previous Message | Jan Wieck | 2002-03-11 20:20:43 | Re: Referential Integrity Triggers |