Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dpIxd-0007Vh-GU for pgsql-admin@arkaria.postgresql.org; Tue, 05 Sep 2017 18:52:33 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dpIxd-0003LK-33 for pgsql-admin@arkaria.postgresql.org; Tue, 05 Sep 2017 18:52:33 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dpIvo-0007kY-Ho for pgsql-admin@postgresql.org; Tue, 05 Sep 2017 18:50:40 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dpIvd-0005zQ-LF for pgsql-admin@postgresql.org; Tue, 05 Sep 2017 18:50:39 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 81F9B20CAA; Tue, 5 Sep 2017 14:50:28 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Tue, 05 Sep 2017 14:50:28 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=WzVltMj3Qxnb7Us1HOXWUNXqt7d2A3Iop1cO9fYgNiU=; b=lwMcmJay Rb9Nlnzn/zlw3lqcMkCR+Q9adHIPd52/yuQ0KijS1dPFT4fS5ljyc4vLchMoyjJQ KaEaYzULikUGB7ECzHEUOeTgfRTW8ZTjGGJ4f4PksQciXKUvDYLlGV4+YnxUFRyB hmw+JgIFS5teKthTEROkrevYwmLIYDvL7Z1A1oaTY+vIv69E+aCWLKUtpxUlfSPL ZWEGvDHY7wOe1QCBZ6KPdTlUyykYTjRf4mfBmkdcXg5a715IP9GDW7jOFaUh1K4e ICYlhhWB9urTyxTr8Ta2iKbXNIcefO733umzTeIfw1Yr+9+mJqqQbpU4Q8t3BTc3 tvT3ulOasbZFbg== X-ME-Sender: X-Sasl-enc: zFbToYOW1oh6vo0IDgmEwQ2z5wRno5EXlHUdUoKYO+qm 1504637428 Received: from april.local (c-73-13-66-39.hsd1.pa.comcast.net [73.13.66.39]) by mail.messagingengine.com (Postfix) with ESMTPA id 280A87FA61; Tue, 5 Sep 2017 14:50:28 -0400 (EDT) Subject: Re: Fastest Backup Method? To: Artem Tomyuk , pgsql-admin@postgresql.org References: From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: Date: Tue, 5 Sep 2017 14:50:27 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org On 9/4/17 13:23, Artem Tomyuk wrote: > I'am wondering, what is the fastest backup method do you know, for me it is: > (Assume that we running on 16 * CPU  box) > > pg_dump -Z 4 -j 16 -F c -F d  > > -Z 4 compression level > > -j 16 number of parallel jobs > > -F c, d  custom+directory format  I think you misunderstood that last part. There can only be one output format, and the last option wins. So you are really running in directory format only. As for performance, you generally have the right idea. Specifics depend on the hardware. My experience is that any compression at all can be bad for performance. But the I/O cost might balance that in some cases. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin