X-Original-To: pgsql-advocacy-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id E3F04D1C9F3 for ; Fri, 23 Apr 2004 12:04:08 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 50876-05 for ; Fri, 23 Apr 2004 12:04:05 -0300 (ADT) Received: from net2.micro-automation.com (net2.micro-automation.com [64.7.141.29]) by svr1.postgresql.org (Postfix) with SMTP id 5587CD1C9B4 for ; Fri, 23 Apr 2004 12:04:04 -0300 (ADT) Received: (qmail 10253 invoked from network); 23 Apr 2004 15:03:58 -0000 Received: from dcdsl.ebox.com (HELO ?192.168.1.36?) (davec@64.7.143.116) by net2.micro-automation.com with SMTP; 23 Apr 2004 15:03:58 -0000 Subject: Re: [HACKERS] What can we learn from MySQL? From: Dave Cramer Reply-To: pg@fastcrypt.com To: "Matthew T. O'Connor" Cc: Fabien COELHO , Bruce Momjian , PostgreSQL-development , PostgreSQL advocacy In-Reply-To: <58232.192.154.91.225.1082725121.squirrel@192.154.91.225> References: <200404230409.i3N49jC02890@candle.pha.pa.us> <58232.192.154.91.225.1082725121.squirrel@192.154.91.225> Content-Type: text/plain Organization: Cramer Consulting Message-Id: <1082732840.13948.45.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Fri, 23 Apr 2004 11:07:20 -0400 Content-Transfer-Encoding: 7bit X-AntiVirus: scanned for viruses by AMaViS 0.2.1 (http://amavis.org/) X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200404/220 X-Sequence-Number: 4192 Does the current implementation of pg_autovacuum have a way of setting windows where it is allowed to vacuum? Many large 24/7 will only allow vacuumming at certain times of the day. Dave On Fri, 2004-04-23 at 08:58, Matthew T. O'Connor wrote: > > There are two issues here : ease-of-use for admin and basic users. > > > > On for former point, admin ease-of-use, A little story a few month ago. > > > > I succeeded in advising production people here to switch some applications > > from a mysql database, which was working perfectly, to a postgres > > database. A few weeks later, the performances were desastrous. 30 seconds > > to get an answer to a simple select on a 1500 entries tables. After > > investigation, the problems were: > > > > - no vacuum, although there were daily "DELETE FROM tables;" > > to empty all the data and reload from another source. > > > > - no analyze, because the admin did not know about it. > > My goal is to have pg_autovacuum integrated into the backend for 7.5. I > don't know if it will default to being turned on or off, I'm sure that > will be a discussion, but if it is defaulted to on, then this whole > problem of having to train newbies about vacuum should just go away. > > Matthew > > > ---------------------------(end of broadcast)--------------------------- > TIP 5: Have you checked our extensive FAQ? > > http://www.postgresql.org/docs/faqs/FAQ.html > > > > !DSPAM:40892fd393131228097780! > > -- Dave Cramer 519 939 0336 ICQ # 14675561