X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 324ABD1B1A1 for ; Fri, 11 Jun 2004 10:55:56 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 22232-06 for ; Fri, 11 Jun 2004 13:55:58 +0000 (GMT) Received: from xtecnica.com (host154-218.pool80206.interbusiness.it [80.206.218.154]) by svr1.postgresql.org (Postfix) with ESMTP id 55BA8D1B1B9 for ; Fri, 11 Jun 2004 10:55:50 -0300 (ADT) Received: from DOMENICO2K by xtecnica.com (MDaemon.PRO.v7.1.0.R) with ESMTP id md50000021078.msg for ; Fri, 11 Jun 2004 15:53:59 +0200 Message-ID: <003901c44fbb$a6f02090$70c8007e@xtecnica.it> Reply-To: "Domenico Sgarbossa" From: "Domenico Sgarbossa" To: Subject: Problems with vacuum! Date: Fri, 11 Jun 2004 15:54:44 +0200 Organization: XTECNICA srl MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0036_01C44FCC.6A2FB290" X-Priority: 1 X-MSMail-Priority: High X-Mailer: Microsoft Outlook Express 5.50.4927.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4927.1200 X-Authenticated-Sender: domenico@xtecnica.com X-Spam-Processed: xtecnica.com, Fri, 11 Jun 2004 15:53:59 +0200 (not processed: message from valid local sender) X-MDRemoteIP: 126.0.200.112 X-Return-Path: domenico@xtecnica.com X-MDaemon-Deliver-To: pgsql-performance@postgresql.org X-MDAV-Processed: xtecnica.com, Fri, 11 Jun 2004 15:54:00 +0200 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=1.2 tagged_above=0.0 required=5.0 tests=HTML_50_60, HTML_MESSAGE, X_MSMAIL_PRIORITY_HIGH, X_PRIORITY_HIGH X-Spam-Level: * X-Archive-Number: 200406/125 X-Sequence-Number: 7183 This is a multi-part message in MIME format. ------=_NextPart_000_0036_01C44FCC.6A2FB290 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I'm running postgrSQL 7.2 on a linux Red Hat 8.0 box with 2GB of RAM=20 When I boot-up the system , this is the TOP situation: 11:59am up 4 min, 1 user, load average: 0.37, 0.26, 0.11 77 processes: 74 sleeping, 3 running, 0 zombie, 0 stopped CPU states: 0.3% user, 0.7% system, 0.0% nice, 98.8% idle Mem: 1031020K av, 177808K used, 853212K free, 0K shrd, 14744K bu= ff Swap: 2096472K av, 0K used, 2096472K free 67828K ca= ched After I've done a vacuum , the situation is: =20 12:04pm up 8 min, 1 user, load average: 0.22, 0.23, 0.12 78 processes: 76 sleeping, 2 running, 0 zombie, 0 stopped CPU states: 2.5% user, 1.9% system, 0.0% nice, 95.4% idle Mem: 1031020K av, 1016580K used, 14440K free, 0K shrd, 18624K bu= ff Swap: 2096472K av, 0K used, 2096472K free 833896K ca= ched As you see the memory used by vacuum isn't released anymore? Anyone know wh= y? My statement is: vacuumdb --analyze dbname My pg paramaters on postgresql.conf are: # # Shared Memory Size # shared_buffers =3D 2048 # 2*max_connections, min 16 max_fsm_relations =3D 100 # min 10, fsm is free space map max_fsm_pages =3D 10000 # min 1000, fsm is free space map max_locks_per_transaction =3D 64 # min 10 wal_buffers =3D 8 # min 4 # # Non-shared Memory Sizes # sort_mem =3D 512 # min 32 vacuum_mem =3D 8192 # min 1024 Did anyone know why this happend?=20 Distinti Saluti Sgarbossa Domenico X Tecnica S.R.L. www.xtecnica.com Tel: 049/9409154 - 049/5970297 Fax: 049/9400288 ------=_NextPart_000_0036_01C44FCC.6A2FB290 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I'm running postgrSQL 7.2 on a linux Red H= at 8.0=20 box with 2GB of RAM
When I boot-up the system , this is the TO= P=20 situation:

11:59am  up 4 min,  1 user,  load average: 0.37, 0.26,=20 0.11

77 processes= : 74=20 sleeping, 3 running, 0 zombie, 0 stopped

CPU states:<= SPAN=20 style=3D"mso-spacerun: yes">  0.3% user,  0.7% system,  0.0% nice, 98.8%=20 idle

Mem:  1031020K av,  177808K used,  853212K free,       0K= =20 shrd,   14744K=20 buff

Swap: 209647= 2K=20 av,      = =20 0K used, 2096472K free        = ;          =20 67828K cached

After I've done a vacuum , the situation= =20 is:
 
&n= bsp;

 12:04pm  up 8 min,  1 user,  load average: 0.22, 0.23,=20 0.12

78 processes= : 76=20 sleeping, 2 running, 0 zombie, 0 stopped

CPU states:<= SPAN=20 style=3D"mso-spacerun: yes">  2.5% user,  1.9% system,  0.0% nice, 95.4%=20 idle

Mem:  1031020K av, 1016580K used,   14440K free,       0K= =20 shrd,   18624K=20 buff

Swap: 209647= 2K=20 av,      = =20 0K used, 2096472K free        = ;         =20 833896K cached

As you see the memory used by vacuum isn't released anymore? Anyone kn= ow=20 why?
 
My statement is: vacuumdb --analyze dbname
My pg paramaters on postgresql.conf are:
 
#
#       Shared Memory=20 Size
#
shared_buffers =3D 2048      &nb= sp; #=20 2*max_connections, min 16
max_fsm_relations =3D 100    # = min 10,=20 fsm is free space map
max_fsm_pages =3D 10000    &nb= sp; #=20 min 1000, fsm is free space map
max_locks_per_transaction =3D 64 # min= =20 10
wal_buffers =3D=20 8            # min= =20 4
 
#
#       Non-shared Memory=20 Sizes
#
sort_mem =3D=20 512            = #=20 min 32
vacuum_mem =3D=20 8192          # min 1024
Did anyone know why this happend?

Distinti Saluti
 
Sgarbossa Domenico
X Tecnica S.R.L.
= www.xtecnica.com
Tel: 049/9409154 -= =20 049/5970297
Fax: 049/9400288
------=_NextPart_000_0036_01C44FCC.6A2FB290--