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 0DF9BD1B341 for ; Tue, 3 Aug 2004 06:07:40 -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 74445-09 for ; Tue, 3 Aug 2004 09:07:31 +0000 (GMT) Received: from mx2.aftenposten.no (mx2.aftenposten.no [80.91.34.76]) by svr1.postgresql.org (Postfix) with ESMTP id 296DFD1B2A8 for ; Tue, 3 Aug 2004 06:07:28 -0300 (ADT) Received: from localhost (localhost.aftenposten.no [127.0.0.1]) by mx2.aftenposten.no (Postfix) with ESMTP id 9E4287F7F1F for ; Tue, 3 Aug 2004 11:07:28 +0200 (CEST) Received: from mx2.aftenposten.no ([127.0.0.1]) by localhost (mx2.aftenposten.no [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 87180-01-4 for ; Tue, 3 Aug 2004 11:07:28 +0200 (CEST) Received: from smtp1.aftenposten.no (unknown [80.91.34.6]) by mx2.aftenposten.no (Postfix) with ESMTP id 05A397F7EFD for ; Tue, 3 Aug 2004 11:07:28 +0200 (CEST) Received: from telecommail.inpoc.no (unverified) by smtp1.aftenposten.no (Content Technologies SMTPRS 4.3.12) with ESMTP id for ; Tue, 3 Aug 2004 11:09:48 +0200 Received: by TELECOMMAIL with Internet Mail Service (5.5.2653.19) id ; Tue, 3 Aug 2004 11:09:27 +0200 Message-ID: From: "Lending, Rune" To: "'pgsql-performance@postgresql.org'" Subject: pg_autovacuum parameters Date: Tue, 3 Aug 2004 11:09:26 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C47939.938C2AB0" X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.5 tagged_above=0.0 required=5.0 tests=HTML_40_50, HTML_MESSAGE X-Spam-Level: X-Archive-Number: 200408/27 X-Sequence-Number: 7663 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C47939.938C2AB0 Content-Type: text/plain Hello all. I am managing a large database with lots of transactions in different tables. The largest tables have around 5-6 millions tuples and around 50000-60000 inserts and maybe 20000 updates pr day. While the smalest tables have only a few tuples and a few updates /inserts pr day. In addition we have small tables with many updates/inserts. So what I am saying is that there is all kinds of tables and uses of tables in our database. This, I think, makes it difficult to set up pg_autovacuum. I am now running vacuum jobs on different tables in cron. What things should I consider when setting but base and threshold values in pg_autovacuum? Since the running of vacuum and analyze is relative to the table size, as it must be, I think it is difficult to cover all tables.. Are there anyone who have some thoughts around this? Regards Rune ------_=_NextPart_001_01C47939.938C2AB0 Content-Type: text/html Melding
Hello all.
 
I am managing a large database with lots of transactions in different tables.
The largest tables have around 5-6 millions tuples and around 50000-60000 inserts and maybe 20000 updates pr day.
While the smalest tables have only a few tuples and a few updates /inserts pr day. In addition we have small tables with many updates/inserts. So what I am saying is that there is all kinds of tables and uses of tables in our database.
This, I think, makes it difficult to set up pg_autovacuum. I am now running vacuum jobs on different tables in cron.
 
What things should I consider when setting but base and threshold values in pg_autovacuum? Since the running of vacuum and analyze is relative to the table size, as it must be, I think it is difficult to cover all tables..
 
Are there anyone who have some thoughts around this?
 
Regards
Rune
 
------_=_NextPart_001_01C47939.938C2AB0--