pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Joshua D. Drake <jd@commandprompt.com>
To: D Kavan <bitsandbytes88@hotmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: vacuumdb -a -f
Date: Wed, 17 Aug 2005 09:15:40 -0700
Message-ID: <430362AC.6010807@commandprompt.com> (raw)
In-Reply-To: <BAY102-F40746DD91FCCD687AF5DF0D1B30@phx.gbl>
References: <BAY102-F40746DD91FCCD687AF5DF0D1B30@phx.gbl>

D Kavan wrote:
> Hi,
> 
> Thanks for the tips.
> 
> Unfortunatley for me,  even after started doing vacuumdb -a 3 times a 
> day and increasing fsm dramatically , the size of the database won't go 
> down even 1 MB.  It's stil at 5.6 GB, size after restore = 4 GB.   I 
> even did a stop/start instead of a re-load to make sure the settings 
> took affect. Would a reboot help?

A vacuum full will decrease the size but I am not sure why the size is a 
problem. I normal vacuum will not remove rows, it only make them 
reusable. So at any given point your database is going to grow after use.

I didn't see this whole thread but is there something specific that 
seems to  be the issue beyond size?

Sincerely,

Joshua D. Drake




> 
> max_fsm_pages = 16000001
> max_fsm_relations = 1000000
> 
> shared_buffers = 65536
> work_mem = 32768
> maintenance work mem = 786432
> 
> checkpoint_segments = 18
> 
> 
> ##/etc/sysctl.conf
> 
> nel.shmall = 524288
> #kernel.shmall = 2097152
> #kernel.shmmax = 2147483648
> #kernel.shmmax = 1073741824
> kernel.shmmax = 6979321856
> kernel.shmmni = 4096
> kernel.sem = 250 32000 100 128
> fs.file-max = 65536
> net.ipv4.ip_local_port_range = 1024 65000
> vm.overcommit_memory = 2
> 
> 
> ~DjK
> 
> 
> 
> 
> 
>> From: Tom Lane <tgl@sss.pgh.pa.us>
>> To: "D Kavan" <bitsandbytes88@hotmail.com>
>> CC: pgsql-admin@postgresql.org
>> Subject: Re: [ADMIN] vacuumdb -a -f Date: Mon, 15 Aug 2005 21:31:01 -0400
>>
>> "D Kavan" <bitsandbytes88@hotmail.com> writes:
>> > Even though I run vacuumdb -a -f every night with no exceptions or 
>> problems,
>> > my database size remains 5.6 GB.  After I do a dump/restore, the new
>> > database size is 4.0 GB.  How could that be possible?
>>
>> The extra 1.6GB probably represents the amount of junk you generate in
>> one day.  So, forget the -f and instead do plain vacuums on a more
>> frequent basis.  Make sure your FSM settings are large enough, too.
>>
>>             regards, tom lane
> 
> 
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend


-- 
Your PostgreSQL solutions company - Command Prompt, Inc. 1.800.492.2240
PostgreSQL Replication, Consulting, Custom Programming, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: plPHP, plPerlNG - http://www.commandprompt.com/



view thread (9+ messages)  latest in thread

Message-ID: <430362AC.6010807@commandprompt.com>
Permalink:  ../430362AC.6010807@commandprompt.com/
Also on:    postgresql.org/message-id/430362AC.6010807@commandprompt.com

 · 

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-admin@postgresql.org
  Cc: jd@commandprompt.com, bitsandbytes88@hotmail.com
  Subject: Re: vacuumdb -a -f
  In-Reply-To: <430362AC.6010807@commandprompt.com>
  References: <BAY102-F40746DD91FCCD687AF5DF0D1B30@phx.gbl> <430362AC.6010807@commandprompt.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