From: Jim Nasby <jnasby@pervasive.com>
To: Jeff Frost <jeff@frostconsultingllc.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: strange fsm issues
Date: Tue, 27 Jun 2006 19:22:01 -0500
Message-ID: <9F858089-CCD2-4F88-BA18-8738ECEF5246@pervasive.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0606231530500.27250@glacier.frostconsultingllc.com>
References: <Pine.LNX.4.64.0606210915370.27250@glacier.frostconsultingllc.com>
<Pine.LNX.4.64.0606211425580.27250@glacier.frostconsultingllc.com>
<Pine.LNX.4.64.0606220750310.4350@discord.home.frostconsultingllc.com>
<D9E39C0B-1D32-4BA6-AEAE-1E2D42ABD3F1@pervasive.com>
<Pine.LNX.4.64.0606221944560.4350@discord.home.frostconsultingllc.com>
<Pine.LNX.4.64.0606231530500.27250@glacier.frostconsultingllc.com>
On Jun 23, 2006, at 5:31 PM, Jeff Frost wrote:
> On Thu, 22 Jun 2006, Jeff Frost wrote:
>> On Thu, 22 Jun 2006, Jim Nasby wrote:
>>>> CPU 0.00s/0.00u sec elapsed 0.00 sec.
>>>> INFO: free space map contains 3339998 pages in 125 relations
>>>> DETAIL: A total of 3341600 page slots are in use (including
>>>> overhead).
>>>> 3341600 page slots are required to track all free space.
>>>> Current limits are: 3366499 page slots, 2000 relations, using
>>>> 19853 KB.
>
> So, now after setting it so high and seeing the above output, we
> ran vacuum verbose again today to check it and it looks like this now:
>
> CPU 0.00s/0.00u sec elapsed 0.00 sec.
> INFO: free space map contains 27804 pages in 125 relations
> DETAIL: A total of 29600 page slots are in use (including overhead).
> 29600 page slots are required to track all free space.
> Current limits are: 3366499 page slots, 2000 relations, using
> 19853 KB.
>
> What the heck? Why would it have shrunk down so much? The vacuum
> full isn't scheduled until tonight. :-/
Take a look at the source for autovacuum... I'm guessing you're right
and that it doesn't make any special considerations for toast tables,
which it probably should (since AFAIK you have to first vacuum the
base table, then commit, then vacuum the toast table).
BTW, tracking pg_class.relpages or actual file size over time would
probably be helpful.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: jnasby@pervasive.com, jeff@frostconsultingllc.com
Subject: Re: strange fsm issues
In-Reply-To: <9F858089-CCD2-4F88-BA18-8738ECEF5246@pervasive.com>
References: <Pine.LNX.4.64.0606210915370.27250@glacier.frostconsultingllc.com> <Pine.LNX.4.64.0606211425580.27250@glacier.frostconsultingllc.com> <Pine.LNX.4.64.0606220750310.4350@discord.home.frostconsultingllc.com> <D9E39C0B-1D32-4BA6-AEAE-1E2D42ABD3F1@pervasive.com> <Pine.LNX.4.64.0606221944560.4350@discord.home.frostconsultingllc.com> <Pine.LNX.4.64.0606231530500.27250@glacier.frostconsultingllc.com> <9F858089-CCD2-4F88-BA18-8738ECEF5246@pervasive.com>
* 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