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 1fuhAn-0001Yd-QZ for pgsql-admin@arkaria.postgresql.org; Tue, 28 Aug 2018 16:48:58 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fuhAm-0004qL-6H for pgsql-admin@arkaria.postgresql.org; Tue, 28 Aug 2018 16:48:56 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fuhAl-0004q7-Ry for pgsql-admin@lists.postgresql.org; Tue, 28 Aug 2018 16:48:55 +0000 Received: from mail-oi0-x243.google.com ([2607:f8b0:4003:c06::243]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1fuhAj-0007iv-6I for pgsql-admin@lists.postgresql.org; Tue, 28 Aug 2018 16:48:55 +0000 Received: by mail-oi0-x243.google.com with SMTP id r69-v6so4062759oie.3 for ; Tue, 28 Aug 2018 09:48:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding:content-language; bh=tiu90zb/y2Ut5qG3hDnDJX/Lm6oaL3rxFTlhYERoWTQ=; b=gjAMC7Zu2j8cEJA6CdQgv6E+FpKHojFsNYNGhFQm9gewTLRlohdxdcaVnhnJf6Gvra 23eg2yU9IRg5d3HrECKoVX14xcAP0nSCmNOHn0Esxy2iBbU+X68th3guD5O16cfF5kPk T0nRnxSBdJK7Z0Eje926q0nqMa2z6uYGRtQrLCUwlgXBLa2XEzUqFqv2uzg6deTTVoSD QRy7iUAaOZ8zf3uJ0dC/n2i/ighIwpaPBYCYGnrVcfw7orXwDlQ/5DTrboQV/jySIkB2 3EWFSkREDXwxVjeti7D8wPj/7PSLkFG4hv59i5J8pPvib3xG4NliF3PQakFNkOC4w/Vv d7PA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding:content-language; bh=tiu90zb/y2Ut5qG3hDnDJX/Lm6oaL3rxFTlhYERoWTQ=; b=LHL1qvnya4AjLOjFTTf7NIcaoSVc3O92jBDpMNPn6SsLXAg9Tlna0ZNAAF3X4x1ddA cD8XSyzsjZ47EQiOsBL8sa2CSL/Pi5oet52RmyOCA+qi6clY9/sE0zX2Pxfjr/3cK5IM wvtz5WVe/Z7Sg49YC9qocpmrg7wv+pro73FdMmnKU9uPAY4iOMAAESQZRqrwgOsgHRyj rZzarmppCSyiwSPNJdPjp+0DyloXFUNRwjmTcbMEZYYAG4WQjJp/WUF7QjrHcA0OPISX 0s80lHon1GYoGBYbe6n6TZzzNIeqYN6CLXmTWxPJSq9zE6OLKBxsp2QrOfey2KlGvXsB IKJg== X-Gm-Message-State: APzg51AU3dYVZ8maQbHMZRXYFJ09ytV35SDB5Vs8rdebw+xopYBtO1we wuA14wzsuSEq+4vcFZatGYhApZyD X-Google-Smtp-Source: ANB0VdZVU4vYUClVJJwYE3UaBZ1voo3EVzlu49QczdcAxlX1UbYnx9BLg0J/Jen09d7IbGhB9jKNqQ== X-Received: by 2002:aca:b256:: with SMTP id b83-v6mr2017451oif.235.1535474930052; Tue, 28 Aug 2018 09:48:50 -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 n15-v6sm692486oic.33.2018.08.28.09.48.48 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 28 Aug 2018 09:48:49 -0700 (PDT) To: pgsql-admin@lists.postgresql.org From: Ron Subject: More efficient pg_restore method? Message-ID: <44555188-c787-b441-5c69-c56f72905bf4@gmail.com> Date: Tue, 28 Aug 2018 11:48:48 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 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 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.) -- Angular momentum makes the world go 'round.