From: Alvaro Herrera <alvherre@commandprompt.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Chris Hoover <revoohc@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Why so long between archive calls?
Date: Fri, 1 Sep 2006 21:40:10 -0400
Message-ID: <20060902014010.GA14288@alvh.no-ip.org> (raw)
In-Reply-To: <25848.1157153334@sss.pgh.pa.us>
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>
Tom Lane wrote:
> "Chris Hoover" <revoohc@gmail.com> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: alvherre@commandprompt.com, tgl@sss.pgh.pa.us, revoohc@gmail.com
Subject: Re: Why so long between archive calls?
In-Reply-To: <20060902014010.GA14288@alvh.no-ip.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> <20060902014010.GA14288@alvh.no-ip.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox