Re: 8.3 / 8.2.6 restore comparison

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, 22 Feb 2008 12:54:00 -0500
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> "Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
> > Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> >> IIRC we were speculating that data was being written
> >> in a pattern that required a lot of seeking thus ruining
> >> throughput, but we didn't have any hard evidence of that. Did you
> >> do the strace'ing I suggested?
>
> > Yes, I asked if you wanted counts or the whole output. You didn't
> > answer :). I provided the counts.
>
> Uh, sorry. Counts are useless here, we need to see the sequence of
> write locations to find out if there's a lot of nonconsecutive
> writes happening. BTW, the strace had better run across the whole
> PG process tree --- it's quite possible that there's some interaction
> between the bgwriter and the backend doing COPY, for instance.

So you want an strace on postmaster not the connection?

Sincerely,

Joshua D. Drake

- --
The PostgreSQL Company since 1997: http://www.commandprompt.com/
PostgreSQL Community Conference: http://www.postgresqlconference.org/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL SPI Liaison | SPI Director | PostgreSQL political pundit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHvw7DATb/zqfZUUQRAoB0AJ9motp+YpW8A4jlu03VsiaLHRIxAACfQ+tO
ZDXUqBcR5e7xsgPnKju9AZc=
=q3FH
-----END PGP SIGNATURE-----