Re: PG_DUMP very slow because of STDOUT ?? - Mailing list pgsql-general

From Andras Fabian
Subject Re: PG_DUMP very slow because of STDOUT ??
Date
Msg-id B1A1AD14D5F9D647BD2A00988C53B8220ACA24C2@atradaex03.nbg.atrada.net
Whole thread Raw
In response to Re: PG_DUMP very slow because of STDOUT ??  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Hi Tom (or others),

are there some recommended settings/ways to use oprofile on a situation like this??? I got it working, have seen a
firstprofile report, but then managed to completely freeze the server on a second try with different oprofile settings
(nexttests will go against the newly installed - next and identical - new servers).  

Andras Fabian

-----Ursprüngliche Nachricht-----
Von: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Gesendet: Freitag, 9. Juli 2010 15:39
An: Andras Fabian
Cc: pgsql-general@postgresql.org
Betreff: Re: [GENERAL] PG_DUMP very slow because of STDOUT ??

Andras Fabian <Fabian@atrada.net> writes:
> Now I ask, whats going on here ???? Why is COPY via STDOUT so much slower on out new machine?

Something weird about the network stack on the new machine, maybe.
Have you compared the transfer speeds for Unix-socket and TCP connections?

On a Red Hat box I would try using oprofile to see where the bottleneck
is ... don't know if that's available for Ubuntu.

            regards, tom lane

pgsql-general by date:

Previous
From: Jayadevan M
Date:
Subject: Re: Queries about PostgreSQL PITR
Next
From: Fujii Masao
Date:
Subject: Re: Queries about PostgreSQL PITR