From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on yquem.inria.fr X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=AWL autolearn=disabled version=3.1.3 X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by yquem.inria.fr (Postfix) with ESMTP id DF31DBBCA for ; Fri, 29 Feb 2008 15:09:06 +0100 (CET) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAAGGgx0dCm3xrnWdsb2JhbACQbwEBAQEBCg8InGU X-IronPort-AV: E=Sophos;i="4.25,426,1199660400"; d="scan'208";a="9749976" Received: from www.janestcapital.com (HELO smtp.janestcapital.com) ([66.155.124.107]) by mail3-smtp-sop.national.inria.fr with ESMTP; 29 Feb 2008 15:09:06 +0100 Received: from [172.25.129.161] [38.96.172.125] by janestcapital.com with ESMTP (SMTPD-9.10) id A1FF0394; Fri, 29 Feb 2008 09:09:03 -0500 Message-ID: <47C811FC.3000807@janestcapital.com> Date: Fri, 29 Feb 2008 09:09:00 -0500 From: Brian Hurt User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: caml-list@yquem.inria.fr Subject: Re: [Caml-list] Long-term storage of values References: <191751.36007.qm@web54607.mail.re2.yahoo.com> <20080229084000.2d3a95fe@tatanka.kerneis.info> <20080229114453.GA19532@annexia.org> In-Reply-To: <20080229114453.GA19532@annexia.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam: no; 0.00; vacuum:98 attendent:98 wrote:01 caml-list:01 off-topic:02 brian:05 brian:05 i'd:06 consuming:88 explain:11 statement:13 but:14 add:14 slow:15 use:16 Richard Jones wrote: >A good first step for PostgreSQL is to use and understand the "VACUUM" >and "EXPLAIN" commands, and to turn on statement logging (with >timestamps) so you can see which queries are consuming the most time. > > > I'd add the "COPY" command to that list, with the attendent understand of why INSERTs are slow on Postgresql. But this is off-topic for this list. Brian