Re: BLOB updates -> database size explodes

From: Luca Ferrari <fluca1978(at)infinito(dot)it>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: BLOB updates -> database size explodes
Date: 2013-05-30 12:45:49
Message-ID: CAKoxK+520UfAMzO-x7u2W7_RHHVdjez8EHKb7PBQhq9B1HsMDg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, May 30, 2013 at 12:49 AM, Stephen Scheck
<singularsyntax(at)gmail(dot)com> wrote:

> If this hypothesis is correct, doing a vacuum should free up dead pages and
> your size expectations should be more accurate. And if that's the case
> putting more intelligence into the application could mitigate some of the
> update growth (predicting what page temporally similar updates will go to
> and grouping them into a single transaction, for instance).
>

Seems correct to me, according to this
http://www.postgresql.org/docs/current/static/lo.html
I would give a try to vacuumlo to see if the size decreases, in such
case that is the right explaination.

Luca

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Chris Angelico 2013-05-30 12:48:50 Re: Introduction
Previous Message Ray Stell 2013-05-30 12:42:21 Re: [GENERAL] pg_upgrade -u