[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-general
Subject:    Re: [GENERAL] BLOB updates -> database size explodes
From:       Luca Ferrari <fluca1978 () infinito ! it>
Date:       2013-05-30 12:45:49
Message-ID: CAKoxK+520UfAMzO-x7u2W7_RHHVdjez8EHKb7PBQhq9B1HsMDg () mail ! gmail ! com
[Download RAW message or body]

On Thu, May 30, 2013 at 12:49 AM, Stephen Scheck
<singularsyntax@gmail.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


-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
[prev in list] [next in list] [prev in thread] [next in thread]