From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Chris Hoover <revoohc(at)gmail(dot)com>, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Why so long between archive calls? |
Date: | 2006-09-02 01:40:10 |
Message-ID: | 20060902014010.GA14288@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Tom Lane wrote:
> "Chris Hoover" <revoohc(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-09-02 01:48:25 | Re: Why so long between archive calls? |
Previous Message | Tom Lane | 2006-09-01 23:28:54 | Re: Why so long between archive calls? |