From: Matthew T. O'Connor <matthew@zeut.net>
To: Otto Blomqvist <o.blomqvist@secomintl.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: pg_autovacuum not having enough suction ?
Date: Thu, 24 Mar 2005 18:40:44 -0500
Message-ID: <42434FFC.10105@zeut.net> (raw)
In-Reply-To: <d1vgq6$31j2$1@news.hub.org>
References: <d1v0a7$iau$1@news.hub.org>
<4933.1111692779@sss.pgh.pa.us>
<d1vgq6$31j2$1@news.hub.org>
The version that shipped with 8.0 should be fine. The only version that
had the problem Tom referred to are in the early 7.4.x releases.
Did you get my other message about information from the stats system
(I'm not sure why my other post has yet to show up on the performance
list).
Matthew
Otto Blomqvist wrote:
>Sorry about that. I'm Running 8.0.0 on Linux Redhat 8.0
>
>
>"Tom Lane" <tgl@sss.pgh.pa.us> wrote in message
>news:4933.1111692779@sss.pgh.pa.us...
>
>
>>"Otto Blomqvist" <o.blomqvist@secomintl.com> writes:
>>
>>
>>>Over 100'000 Index Rows removed, 300'000 unused item pointers ? How
>>>
>>>
>could
>
>
>>>autovacuum let this happen ?
>>>
>>>
>>What PG version is this?
>>
>>(The earlier autovacuum releases had some bugs with large tables, thus
>>the question...)
>>
>>regards, tom lane
>>
>>---------------------------(end of broadcast)---------------------------
>>TIP 6: Have you searched our list archives?
>>
>> http://archives.postgresql.org
>>
>>
>>
>
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 7: don't forget to increase your free space map settings
>
>
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: matthew@zeut.net, o.blomqvist@secomintl.com
Subject: Re: pg_autovacuum not having enough suction ?
In-Reply-To: <42434FFC.10105@zeut.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox