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 2B24E9F9F66 for ; Fri, 1 Sep 2006 20:37:19 -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 54176-01-6 for ; Fri, 1 Sep 2006 20:36:45 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 0C4A49FB32E for ; Fri, 1 Sep 2006 20:28:55 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k81NSsd4025849; Fri, 1 Sep 2006 19:28:54 -0400 (EDT) To: "Chris Hoover" cc: pgsql-admin@postgresql.org Subject: Re: Why so long between archive calls? In-reply-to: <1d219a6f0609011230t2407cba5u53a5e536ad4fbc20@mail.gmail.com> 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> Comments: In-reply-to "Chris Hoover" message dated "Fri, 01 Sep 2006 15:30:53 -0400" Date: Fri, 01 Sep 2006 19:28:54 -0400 Message-ID: <25848.1157153334@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.124 tagged_above=0 required=5 tests=AWL, SPF_HELO_PASS, SPF_PASS X-Spam-Level: X-Archive-Number: 200609/14 X-Sequence-Number: 22928 "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. regards, tom lane