wrote:
Horaci Macias wrote:
after tuning the autovacuum settings I can now see the tables vaccumed
and the number of dead tuples dropping whenever an autovacuum happens,
which makes sense.
Great.
What I don't see though is the size of the tables ever decreasing, but
I'm not sure I
much is occupied by live tuples?
H
On 10/05/12 16:50, Albe Laurenz wrote:
Horaci Macias wrote:
I'm running postgres 9.1 and having disk space problems.
My application captures information 24x7 and stores it into the
database. This includes several bytea and can be ~5M entries a day, so
the child table constraints to
search all the child tables that could contain data.
Guy
On May 10, 2012, at 11:01 AM, Horaci Macias wrote:
thanks Guy. I had thought about using per-day tables (although I didn't know
about child tables) but my problem is that some entries are related and
o the end of day / start of day time.
Anyway, worth a thought for sure so thanks.
H
On 10/05/12 16:42, Guy Helmer wrote:
On May 10, 2012, at 4:31 AM, Horaci Macias wrote:
Hi everybody,
I'm running postgres 9.1 and having disk space problems.
My application captures information 24x7 and
till be a problem even if
last_autovacuum shows autovacuum ran?
thanks,
H
On 10/05/12 16:50, Albe Laurenz wrote:
Horaci Macias wrote:
I'm running postgres 9.1 and having disk space problems.
My application captures information 24x7 and stores it into the
database. This includes several byte
Hi everybody,
I'm running postgres 9.1 and having disk space problems.
My application captures information 24x7 and stores it into the
database. This includes several bytea and can be ~5M entries a day, so
the size can be an issue after several days.
My application also cleans up entries older
