Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fvQmB-0001MO-Sm for pgsql-admin@arkaria.postgresql.org; Thu, 30 Aug 2018 17:30:36 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fvQm9-0004QO-LF for pgsql-admin@arkaria.postgresql.org; Thu, 30 Aug 2018 17:30: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.89) (envelope-from ) id 1fvQm9-0004QH-7v for pgsql-admin@lists.postgresql.org; Thu, 30 Aug 2018 17:30:33 +0000 Received: from mail-oi0-x244.google.com ([2607:f8b0:4003:c06::244]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1fvQm6-0001Dh-IK for pgsql-admin@lists.postgresql.org; Thu, 30 Aug 2018 17:30:31 +0000 Received: by mail-oi0-x244.google.com with SMTP id m11-v6so16883009oic.2 for ; Thu, 30 Aug 2018 10:30:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:from:to:references:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=038sxEPaLsgwG9s0baMWR6x5laPAHjIX5hTyT9U/+pY=; b=YqhTaHoh5sJxwzhrqvLUavGyt2PzpjLOMe8GhoA1K9Gcz4k465SZbJtgBZ53kc0C8D tMbwtXbG5KPODZY74SUg/6mgqBqtms71qSpjJd0ruGU0y3MVKIRpd4hrkGksIcA09l7p WAxnDDYo4oB3+OPcwxUQ5LXear9ib3fV8+oRYlJeKA7OYE8crbR/RoCH2wwA1FemhzYl KmVnVSg4RRs1/+NjpTayWgKqDBf0SRy5Qvo9fX/vezZBWU4fSES7kBY03xtHar2j74jV fJzFUgAZGNpXONRcV/wguB2K4JLfEXsOmihAyGxZqUowc7ilKzhEFWMQUN7FIR7YqQAu Ya9A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:from:to:references:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=038sxEPaLsgwG9s0baMWR6x5laPAHjIX5hTyT9U/+pY=; b=MYqm2cyeyrvkRckzi7OIs1+Q88nhZc6St+/fhstyZ5rIB/XfBel84a1EUsjIMiTRvy om7tOpK7kFVjnp1YoiUhCMrEwRFkD9YUe67uK4/xLCuMP/OLn1C96RlXVZFFmSf0LfYd a4i9H/4H7v2By9e/hngvNWe/eP9wUPkzkKxRaEM8B0aNm5gkC34FyjDhc3nRZFgTekSh /ScyG/tmu5L0W1pM5LkAPF2BlATKPOqvv/k0pmYn4grTrzhtYIDbAdpajF8E7n/cw638 rQWkYLqm1JsLnEcifyBN4xeVL0tloGd6N610rQQ0XkARV6NRcfnb7VTU5IslBXy7IIlW 6OUQ== X-Gm-Message-State: APzg51C0cVHaM/h3abOY5JuI9uoekg6HVvloZ+oubktvUhFznvU3LMWd WyjdsrBPTcFlei4V7y+QHhF1q2ex X-Google-Smtp-Source: ANB0VdbvYVLbbnZISGTzqduBxg0p1qOdbokGyq08XBwKWCdLOvfBAbkA+Ua0yRmO2b0tXu+PQ2ehKQ== X-Received: by 2002:aca:4ed3:: with SMTP id c202-v6mr3735926oib.92.1535650229264; Thu, 30 Aug 2018 10:30:29 -0700 (PDT) Received: from [192.168.1.10] (ip70-171-116-89.no.no.cox.net. [70.171.116.89]) by smtp.googlemail.com with ESMTPSA id j16-v6sm6144761oib.42.2018.08.30.10.30.27 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 30 Aug 2018 10:30:28 -0700 (PDT) Subject: Re: More efficient pg_restore method? From: Ron To: pgsql-admin@lists.postgresql.org References: <44555188-c787-b441-5c69-c56f72905bf4@gmail.com> Message-ID: Date: Thu, 30 Aug 2018 12:30:27 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <44555188-c787-b441-5c69-c56f72905bf4@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 08/28/2018 11:48 AM, Ron wrote: > > Pg 9.6.9 on Linux... > > Given a backup server storing a "format=directory" database backup, and a > database server, should I: > > Option #1: run pg_restore on the backup server and "push" the data to the > database server via port 5432, or > Option #2: have the backup server serve the dump directory via NFS, and > run pg_restore on the database server, pulling the data via nfs protocol? > > (It'll be a multi-threaded restore over a 10Gb pipe.) Turns out that pushing the data over port 5432 is about 3x faster than pulling it across nfs (at least when a WAN is involved). -- Angular momentum makes the world go 'round.