| From: | Ericson Smith <eric(at)did-it(dot)com> |
|---|---|
| To: | Andrew Sullivan <andrew(at)libertyrms(dot)info> |
| Cc: | Postgresql General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: 7.4? |
| Date: | 2003-02-25 14:41:13 |
| Message-ID: | 1046184073.14626.9.camel@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, 2003-02-25 at 08:18, Andrew Sullivan wrote:
> I believe the new vacuum stuff is just to help on btree indexes. The
> current vacuum doesn't lock the tables, either.
I was actually thinking about a VACUUM FULL. Currently we have not
problems doing a regular VACUUM. That said, will the new vacuum free as
much space like the current vacuum full, without the handicap of table
locking?
> It sounds like either your free space map is not set correctly, or
> you have ever-growing indexes. Reindexing would be enough for this
> problem. There are still some 24/7-operation problems with having to
> reindex.
>
We will definitely try the reindex as suggested.
--
Ericson Smith <eric(at)did-it(dot)com>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-02-25 14:43:10 | Re: how do i avoid multiple sessions from inserting the |
| Previous Message | Andrew Perrin | 2003-02-25 14:14:07 | Re: Can postgresql be run in memory (like a memory resident |