pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Karim Nassar <karim.nassar@acm.org>
To: pgsql-performance@postgresql.org
Subject: VACUUM on duplicate DB gives FSM and total pages discrepancies
Date: Tue, 29 Mar 2005 17:52:58 -0700
Message-ID: <1112143978.9077.29.camel@k2.cet.nau.edu> (raw)

I recently pg_dumpall'd my DB from a (used for testing) v20z install of
postgresql 8.0.1, and restored it to my production (but not yet in
service) v40z running the same version. The test DB has had multiple
millions of rows created/dropped during testing. The results of VACUUM
VERBOSE are giving me pause:

* v40z (hardly used after restore):

orfs=# vacuum full analyze verbose;
<snip>
INFO:  free space map: 114 relations, 84 pages stored; 1824 total pages needed
DETAIL:  Allocated FSM size: 1000 relations + 300000 pages = 1864 kB shared memory.
VACUUM


* v20z (after having undergone extensive tweaking, deletes, and inserts):

orfs=# vacuum full analyze verbose;
<snip>
INFO:  free space map: 53 relations, 13502 pages stored; 9776 total pages needed
DETAIL:  Allocated FSM size: 1000 relations + 300000 pages = 1864 kB shared memory.
VACUUM

1) Should I be concerned about the total pages needed? ISTM that using
that many more pages can't help but degrade relative performance on my
testing machine.

2) How is it that my FSM has different numbers of relations?

3) Are either of these affects normal for an oft-used (or not) DB?

FWIW:
                         v40z      v20z
maintenance_work_mem   262144     16384 
shared_buffers          30000      1000

Thanks,
-- 
Karim Nassar
Department of Computer Science
Box 15600, College of Engineering and Natural Sciences
Northern Arizona University,  Flagstaff, Arizona 86011
Office: (928) 523-5868 -=- Mobile: (928) 699-9221




view thread (2+ messages)  latest in thread

Message-ID: <1112143978.9077.29.camel@k2.cet.nau.edu>
Permalink:  ../1112143978.9077.29.camel@k2.cet.nau.edu/
Also on:    postgresql.org/message-id/1112143978.9077.29.camel@k2.cet.nau.edu

 · 

reply

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-performance@postgresql.org
  Cc: karim.nassar@acm.org
  Subject: Re: VACUUM on duplicate DB gives FSM and total pages discrepancies
  In-Reply-To: <1112143978.9077.29.camel@k2.cet.nau.edu>
  References: <1112143978.9077.29.camel@k2.cet.nau.edu>

* 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