Re: RES: Degradation of postgres 7.4.5 on FreeBSD/CygWin

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
To: Rodrigo Moreno <rodrigo(dot)miguel(at)terra(dot)com(dot)br>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: RES: Degradation of postgres 7.4.5 on FreeBSD/CygWin
Date: 2005-02-18 14:51:42
Message-ID: 421600FE.8090407@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

> this is only max 15 concurrent conections. And is not a heavy performance
> database, so i think this is not necessary vacumm more than once a day.
>
> In another customer, has only 5 users and the database have 300mb, small
> database, and has the same behaviour (haven't modified postgresql).
> My first instalation was not changed anything in postgresql.conf, but in
> this new server (FreeBSD) i have changed some parameters.
>
> as showed in my crontab list, i think this is enough:
> 00 13 * * 1-5 /bin/sh /home/postgres/backup.sh >/dev/null 2>&1
> 00 19 * * 1-5 /bin/sh /home/postgres/backup.sh >/dev/null 2>&1
> 00 23 * * 1-5 /usr/local/pgsql/bin/psql supre -c "vacuum analyze;"

We just told you - it's nowhere near enough. Vacuum once an hour. Size
of the database is not that relevant, its size of changes that is.

Chris

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Christopher Kings-Lynne 2005-02-18 14:52:48 Re: RES: Degradation of postgres 7.4.5 on FreeBSD/CygWin
Previous Message Steinar H. Gunderson 2005-02-18 14:40:21 Re: Degradation of postgres 7.4.5 on FreeBSD/CygWin