Received: from malur.postgresql.org ([217.196.149.56])
 by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from
 <pgsql-admin-owner+M44058=pgsql+2Dadmin=arkaria.postgresql.org@postgresql.org>)
 id 1Yxzie-0002Tp-2N
 for pgsql-admin@arkaria.postgresql.org; Thu, 28 May 2015 15:27:40 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
 by malur.postgresql.org with smtp (Exim 4.80) (envelope-from
 <pgsql-admin-owner+M44058=pgsql+2Dadmin=arkaria.postgresql.org@postgresql.org>)
 id 1Yxzid-00070V-Ad
 for pgsql-admin@arkaria.postgresql.org; Thu, 28 May 2015 15:27:39 +0000
Received: from makus.postgresql.org ([2001:4800:1501:1::229])
 by malur.postgresql.org with esmtps (TLS1.2:RSA_AES_256_CBC_SHA256:256)
 (Exim 4.80) (envelope-from <tgl@sss.pgh.pa.us>) id 1Yxzia-0006vB-Nj
 for pgsql-admin@postgresql.org; Thu, 28 May 2015 15:27:36 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
 by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
 (Exim 4.84) (envelope-from <tgl@sss.pgh.pa.us>) id 1YxziY-0005Na-61
 for pgsql-admin@postgresql.org; Thu, 28 May 2015 15:27:35 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
 by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id t4SFRVFT015002;
 Thu, 28 May 2015 11:27:31 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: girish R G peetle <giri.anamika0@gmail.com>
cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: PostgreSQL Dump based backup using pipe
In-reply-to: 
 <CAKKd066ja0nWoVfxyJKObtngTY0AeXBaLeziVJLUDsAX+qj-qw@mail.gmail.com>
References: 
 <CAKKd066yz3GeEg9D_8KDPGz38YX=rzFAcGd5paUWaOtOqkNsPA@mail.gmail.com>
 <31650.1432736684@sss.pgh.pa.us>
 <CAKKd065aJ1LuUMw_bhBgmgoM6Ng-cLdBobpzRiU+UsdsmW2aOg@mail.gmail.com>
 <2627.1432745444@sss.pgh.pa.us>
 <CAKKd066ja0nWoVfxyJKObtngTY0AeXBaLeziVJLUDsAX+qj-qw@mail.gmail.com>
Comments: In-reply-to girish R G peetle <giri.anamika0@gmail.com>
 message dated "Thu, 28 May 2015 14:40:57 +0530"
Date: Thu, 28 May 2015 11:27:31 -0400
Message-ID: <15001.1432826851@sss.pgh.pa.us>
X-Pg-Spam-Score: -1.9 (-)
List-Archive: <http://archives.postgresql.org/pgsql-admin>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-admin.postgresql.org>
List-Owner: <mailto:pgsql-admin-owner@postgresql.org>
List-Post: <mailto:pgsql-admin@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-admin>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
X-Mailing-List: pgsql-admin
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

girish R G peetle <giri.anamika0@gmail.com> writes:
> I just tracked pg_dump writing output to a file. (using procmon)
> As indicated below data is not written in serial fashion.
> If we use name pipe would this behavior cause problem ?

It's less efficient with a named pipe, yes, because then pg_dump
can't do that.  But this doesn't prove anything one way or another
concerning your original complaint.

			regards, tom lane


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin