Received: from localhost (unknown [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 3EA1F9FB1D9 for ; Thu, 11 Oct 2007 15:30:25 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 94727-08 for ; Thu, 11 Oct 2007 15:30:17 -0300 (ADT) X-Greylist: delayed 00:06:24.972831 by SQLgrey-1.7.5 Received: from mail.autorevenue.com (ip-208.178.167.106.gblx.net [208.178.167.106]) by postgresql.org (Postfix) with ESMTP id 50CB49FA5CF for ; Thu, 11 Oct 2007 15:30:14 -0300 (ADT) Received: (qmail 4498 invoked from network); 11 Oct 2007 14:25:48 -0400 Received: from unknown (HELO D1RPQZB1) (msteben@192.168.1.181) by mail.autorevenue.com with SMTP; 11 Oct 2007 14:25:48 -0400 From: "Mark Steben" To: Subject: postgres 8.2.4 new installation - trying to get autovacuum to work Date: Thu, 11 Oct 2007 14:21:33 -0400 Message-ID: <00b401c80c33$8da81f10$b501a8c0@D1RPQZB1> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00B5_01C80C12.06967F10" X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2992 Thread-Index: AcgMM42QdaZxWQVHSHSSGkleL8mngQ== X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.138 tagged_above=0 required=5 tests=AWL=0.136, BAYES_50=0.001, HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 200710/99 X-Sequence-Number: 27013 This is a multi-part message in MIME format. ------=_NextPart_000_00B5_01C80C12.06967F10 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi, I'm new to 8.2 and trying to get our testing server to autovacuum. I have a table that has roughly 116000 rows I have applied 40,000 updates. The applicable postgresql.conf parameters are as follows: autovacuum | on autovacuum_analyze_scale_factor | 0.1 autovacuum_analyze_threshold | 250 autovacuum_freeze_max_age | 200000000 autovacuum_naptime | 60 autovacuum_vacuum_cost_delay | -1 autovacuum_vacuum_cost_limit | -1 autovacuum_vacuum_scale_factor | 0.2 autovacuum_vacuum_threshold | 500 stats_row_level | on stats_start_collector | on given the scale factor and the threshold I expected autovacuum to kick in at about the 23000 th update I am looking at the pg_logs Should I be looking elsewhere? Log_min_duration_statement currently set to 2000 milliseconds. The updates show in the logs. The vacuum does not. Any help would be appreciated. Thank you, Mark Steben Senior Database Administrator @utoRevenueT A Dominion Enterprises Company 480 Pleasant Street Suite B200 Lee, MA 01238 413-243-4800 Home Office 413-243-4809 Corporate Fax msteben @autorevenue.com Visit our new website at www.autorevenue.com IMPORTANT: The information contained in this e-mail message is confidential and is intended only for the named addressee(s). If the reader of this e-mail message is not the intended recipient (or the individual responsible for the delivery of this e-mail message to the intended recipient), please be advised that any re-use, dissemination, distribution or copying of this e-mail message is prohibited. If you have received this e-mail message in error, please reply to the sender that you have received this e-mail message in error and then delete it. Thank you. ------=_NextPart_000_00B5_01C80C12.06967F10 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi, I’m new to 8.2 and trying to get our testing server to autovacuum.

I have a table that  has roughly 116000 = rows

 I have applied 40,000 = updates.

 

The applicable postgresql.conf parameters are as = follows:

 

 autovacuum        &= nbsp;                       &= nbsp;   | on

 autovacuum_analyze_scale_factor   | = 0.1

 autovacuum_analyze_threshold =       | 250

 autovacuum_freeze_max_age     =     | 200000000

 autovacuum_naptime       = ;               | = 60

 autovacuum_vacuum_cost_delay    | = -1

 autovacuum_vacuum_cost_limit   =    | -1

 autovacuum_vacuum_scale_factor  | = 0.2

 autovacuum_vacuum_threshold   =    | 500

 

stats_row_level        &n= bsp;                    &= nbsp; | on

 stats_start_collector      &n= bsp;               &= nbsp;| on

 

given the scale factor and the threshold I expected autovacuum = to kick in at about the 23000 th update

 

I am looking at the pg_logs   Should I be looking elsewhere?  Log_min_duration_statement currently set to 2000 = milliseconds.

The updates show in the logs.  The vacuum does = not.

 

Any help would be appreciated.  Thank  = you,

 

Mark Steben

Senior Database Administrator
@utoRevenue™
A Dominion = Enterprises Company
480 = Pleasant Street
Suite = B200
Lee, MA 01238
413-243-4800 Home Office 
413-243-4809 Corporate Fax

msteben@autorevenue.com

Visit our = new website at
www.autorevenue.com

 

IMPORTANT: The information = contained in this e-mail message is confidential and is intended only for the named addressee(s). If the reader of this e-mail message is not the intended recipient (or the individual responsible for the delivery of this e-mail message to the intended recipient), please be advised that any re-use, dissemination, distribution or copying of this e-mail message is = prohibited.  If you have received this e-mail message in error, please reply to = the sender that you have received this e-mail message in error and then = delete it.  Thank you.

 

------=_NextPart_000_00B5_01C80C12.06967F10--