| From: | Robert(dot)Farrugia(at)go(dot)com(dot)mt |
|---|---|
| To: | pgsql-admin(at)postgresql(dot)org |
| Subject: | VACUUM possible bug |
| Date: | 2001-06-04 07:44:08 |
| Message-ID: | OF2AB7FD2D.96D3346B-ONC1256A61.0029FBA4@go.com.mt |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Hi to all,
After upgrading to 7.1, I have noticed that when doing a vacuum, the
postmaster usually crashes. Noticed also that the available space is 0
bytes free. The pg_xlog directory then contains a large number fo
WAL-files. Tables size are about 7GB for a total database size of over
50GB.
Question is why do the WAL-files increase during the VACUUM ? I normally
have aroung 15GB free space on the drive, so even if a table is re-copied,
there should still be space ?
Does not vacuum commit after each table, or does it commit after the whole
operation ? If so, is it possible to make vacuum commit after each table
(without doing it manually by vacuuming one table at a time) ?
I'm currently upgrading to 7.1.2, maybe the bug has been fixed in this
version.
Thanks
Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tauren Mills | 2001-06-04 09:16:33 | Limiting simultaneous connections |
| Previous Message | Stefan Huber | 2001-06-02 15:33:46 | Re: Re: Database over multiple drives |