X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 696939FB466 for ; Fri, 1 Sep 2006 22:40:53 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 63482-01 for ; Fri, 1 Sep 2006 22:40:47 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from lists.commandprompt.com (host-130.commandprompt.net [207.173.203.130]) by postgresql.org (Postfix) with ESMTP id 4F3D69FB442 for ; Fri, 1 Sep 2006 22:40:47 -0300 (ADT) Received: from alvh.no-ip.org (201-221-200-187.bk11-dsl.surnet.cl [201.221.200.187]) (authenticated bits=0) by lists.commandprompt.com (8.13.7/8.13.6) with ESMTP id k821emGc012565; Fri, 1 Sep 2006 18:40:49 -0700 Received: by alvh.no-ip.org (Postfix, from userid 1000) id 326A4C2DC58; Fri, 1 Sep 2006 21:40:10 -0400 (CLT) Date: Fri, 1 Sep 2006 21:40:10 -0400 From: Alvaro Herrera To: Tom Lane Cc: Chris Hoover , pgsql-admin@postgresql.org Subject: Re: Why so long between archive calls? Message-ID: <20060902014010.GA14288@alvh.no-ip.org> Mail-Followup-To: Tom Lane , Chris Hoover , pgsql-admin@postgresql.org References: <1d219a6f0608290835u6647a8e1g437dfd4cedb81658@mail.gmail.com> <44F4690D.2010503@mailnetwork.co.uk> <1d219a6f0608290934g6d3ed785oa2814dbf3619306b@mail.gmail.com> <1d219a6f0608301212k699061d0ge52c953ecc5bddfa@mail.gmail.com> <24247.1157059093@sss.pgh.pa.us> <1d219a6f0609011230t2407cba5u53a5e536ad4fbc20@mail.gmail.com> <25848.1157153334@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <25848.1157153334@sss.pgh.pa.us> User-Agent: Mutt/1.5.12-2006-07-14 X-Virus-Scanned: ClamAV version 0.88.3, clamav-milter version 0.88.3 on projects.commandprompt.com X-Virus-Status: Clean X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (lists.commandprompt.com [192.168.2.159]); Fri, 01 Sep 2006 18:40:49 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.284 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200609/15 X-Sequence-Number: 22929 Tom Lane wrote: > "Chris Hoover" writes: > > I just ran this for several minutes and have about an 11MB trace file. Is > > there anything particular you want to see? > > > Also, is the data in the file deciferable or have actual database data in > > it? The reason I ask, is that I work under HIPPA regulations, so I can't > > release anything if it has potential personal/patient data in it. > > Yeah, you probably want to strip out the data portion of any read() or > write() calls shown in the trace. > > BTW, I forgot to ask for timestamp information in the trace --- if you > didn't use -t please do it over. It might be possible to get strace > to skip the read/write data by itself so you don't have to do it > manually, but I don't see anything obvious in its help output. strace -s0 That'll cut any strings though, not only for read/writes. You'll still get file names. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support