Re: PG_DUMP very slow because of STDOUT ??

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andras Fabian <Fabian(at)atrada(dot)net>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: PG_DUMP very slow because of STDOUT ??
Date: 2010-07-09 14:08:54
Message-ID: 18976.1278684534@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Andras Fabian <Fabian(at)atrada(dot)net> writes:
>> Something weird about the network stack on the new machine, maybe.
>> Have you compared the transfer speeds for Unix-socket and TCP connections?

> Hmm, no ... but how do Unix-socket / TCP connections relate to STDOUT here (sorry, maybe this is obvious to some, but not to me at the moment)?

Well, COPY TO STDOUT really means "send the data across the network
connection to the client". It sounds to me like your problem is slow
data transfer between the database backend and pg_dump (or psql).
Not sure what could be causing it, unless perhaps you've got a kernel
packet filter that's performing an unreasonable amount of processing
per packet.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Josip Rodin 2010-07-09 14:26:15 simple functions, huge overhead, no cache
Previous Message Andras Fabian 2010-07-09 13:47:29 Re: PG_DUMP very slow because of STDOUT ??