| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Nikola Milutinovic <Nikola(dot)Milutinovic(at)ev(dot)co(dot)yu> |
| Cc: | PgSQL General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL slow after VACUUM |
| Date: | 2004-11-26 18:34:54 |
| Message-ID: | 10275.1101494094@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Nikola Milutinovic <Nikola(dot)Milutinovic(at)ev(dot)co(dot)yu> writes:
> - PostgreSQL 7.3.2 MDK5
> ...
> A couple of days ago, disk became full, since we were not doing VACUUM
> on the DB at all. So, I deleted all records from the 3 tables the DB has
> and performed "VACUUM FULL ANALYZE". This reclaimed the space.
The subsequent discussion pointed out that you probably shouldn't have
ANALYZEd right at that point, but I didn't see anyone suggest that you
should have done TRUNCATEs rather than delete all/vacuum full. The
TRUNCATE way is a good deal faster, and it will also eliminate index
bloat while vacuum full won't.
BTW, 7.3.2 has several known serious bugs; I'd recommend an update to
7.3.8, if not upgrading to 7.4.*.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | j0rd1 adame | 2004-11-26 18:45:09 | Re: [ok] Error after adding Foreign Keys |
| Previous Message | Tom Lane | 2004-11-26 18:26:59 | Re: pg_dump and languages |