pg.ddx.io pgsql-performance@postgresql.org mailing list archive
help / color / mirror / Atom feedVACUUM on duplicate DB gives FSM and total pages discrepancies
2+ messages / 2 participants
[nested] [flat]
* VACUUM on duplicate DB gives FSM and total pages discrepancies
@ 2005-03-30 00:52 Karim Nassar <karim.nassar@acm.org>
2005-03-30 15:19 ` Re: VACUUM on duplicate DB gives FSM and total pages discrepancies Alvaro Herrera <alvherre@dcc.uchile.cl>
0 siblings, 1 reply; 2+ messages in thread
From: Karim Nassar @ 2005-03-30 00:52 UTC (permalink / raw)
To: pgsql-performance
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
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: VACUUM on duplicate DB gives FSM and total pages discrepancies
2005-03-30 00:52 VACUUM on duplicate DB gives FSM and total pages discrepancies Karim Nassar <karim.nassar@acm.org>
@ 2005-03-30 15:19 ` Alvaro Herrera <alvherre@dcc.uchile.cl>
0 siblings, 0 replies; 2+ messages in thread
From: Alvaro Herrera @ 2005-03-30 15:19 UTC (permalink / raw)
To: Karim Nassar <karim.nassar@acm.org>; +Cc: pgsql-performance
On Tue, Mar 29, 2005 at 05:52:58PM -0700, Karim Nassar wrote:
> 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:
The FSM only stores pages that have some free space. If the database
has only been through a restore, then probably there aren't many of
those. After you start playing with the data some more pages will need
registering. So the behavior you are seeing is expected.
--
Alvaro Herrera (<alvherre[@]dcc.uchile.cl>)
"We are who we choose to be", sang the goldfinch
when the sun is high (Sandman)
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2005-03-30 15:19 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2005-03-30 00:52 VACUUM on duplicate DB gives FSM and total pages discrepancies Karim Nassar <karim.nassar@acm.org>
2005-03-30 15:19 ` Alvaro Herrera <alvherre@dcc.uchile.cl>
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