Обсуждение: vacuum message

Hi:

   I did a vacuum verbose on my database and at the end of the output I got
the following:

INFO:  free space map: 85 relations, 18940 pages stored; 29584 total pages
needed
DETAIL:  Allocated FSM size: 1000 relations + 20000 pages = 186 kB shared
memory.
VACUUM

   Can somebody tell me what that means?

Thanks!

You need to increase your max_fsm_pages to at least 29584 pages to
accommodate / monitor all free pages.

-----Original Message-----
From: pgsql-admin-owner@postgresql.org
[mailto:pgsql-admin-owner@postgresql.org]On Behalf Of Colton A Smith
Sent: Thursday, 22 September 2005 8:00 a.m.
To: pgsql-admin@postgresql.org
Subject: [ADMIN] vacuum message

Hi:

   I did a vacuum verbose on my database and at the end of the output I got
the following:

INFO:  free space map: 85 relations, 18940 pages stored; 29584 total pages
needed
DETAIL:  Allocated FSM size: 1000 relations + 20000 pages = 186 kB shared
memory.
VACUUM

   Can somebody tell me what that means?

Thanks!

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

On 23.09.2005 08:01, Adrian Engelbrecht wrote:
> You need to increase your max_fsm_pages to at least 29584 pages to
> accommodate / monitor all free pages.

Better set it to much more to have some room for future growth, 50000 maybe.


--
Regards,
Hannes Dorbath

On Mon, Sep 26, 2005 at 07:28:30PM +0530, Gourish Singbal wrote:
> Thats a good Idea.
>  My output after full vaccum is :-
>  INFO: free space map: 9 relations, 114736 pages stored; 76592 total pages
> needed
> DETAIL: Allocated FSM size: 1000 relations + 300000 pages = 1856 kB shared
> memory.
> VACUUM
>  I just have a Question:
> Is the allocate pages 300000 okey ?. OR do i need to decrease it to 100000 ?
>  regards

Downside: you're burning extra memory, to the tune of 6 bytes per page.
Downside: there's some additional overhead in maintaining a larger FSM
Upside: you have room to grow, as well as to accommodate occasional
bursts of update activity

Both downsides are pretty minor, I'd say just stick with what you've
got.
--
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