Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fBtYj-0007gi-Um for pgsql-admin@arkaria.postgresql.org; Fri, 27 Apr 2018 02:56:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fBtYi-0006sA-4w for pgsql-admin@arkaria.postgresql.org; Fri, 27 Apr 2018 02:56:28 +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 1fBtYh-0006r9-Rn for pgsql-admin@lists.postgresql.org; Fri, 27 Apr 2018 02:56:27 +0000 Received: from mail-io0-x241.google.com ([2607:f8b0:4001:c06::241]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1fBtYa-0006de-RD for pgsql-admin@postgresql.org; Fri, 27 Apr 2018 02:56:27 +0000 Received: by mail-io0-x241.google.com with SMTP id p124-v6so895432iod.1 for ; Thu, 26 Apr 2018 19:56:19 -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-language; bh=1a+5iciPmkuU+cGtdOaEO8xQifdApceQ7Wai8JpH0Vs=; b=m1GlRykI8W+Nr9d/CFN4E92HeePubzUFufqZnF0Lqy7w+q2Dw/NpcBZ6TWGwqLcc9L c9TPqlxyZjRg5Sds0wlpa2SSQS5hV7o9qj8kAW9UOflwzN1wfyeY3IJLm+VC0LiFOHMc G1RAQuv1DvpW17GKISV/u80YhRBOptwYpBOTOGasJFoDCeq+mZwhaZBEUngzNqU84TIC xkuZqF2eynK12pqg5W4EVU9PoY7d2Ba7qW96iX0SLYke1exWml6L3SjwSVbCM1bzeWDW hmL2xDmxTVzJn3JNc3AzLgkqlPRhe1zzbTbPdMv22R0J/dW5myf27dllpKvch5joRkIZ fOXA== 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-language; bh=1a+5iciPmkuU+cGtdOaEO8xQifdApceQ7Wai8JpH0Vs=; b=Ns6h2ZI2f9LypWS9PPYGWfviGU/oXOem94k8frw2eZ6U2+LISSoVFZDj63iZb+wXxn QUoIkBCyGu32ds8yxBBxx8PfZq4JLFRfK0AmceU+4528f3mHJS1aGmp8M9LqnStSY/1s tQmBxXS/JPIvO//01zS0ph6JTECqJKoRhaCkL4URTU6EWX+lJaaA05BYFk/KhJ6qzabA E7jOhEJ94HzJImJsCYpHHvjWhSCxqDf+lH2g8VaaFfEISrTbxl3qo5J7XN5J2FKHqlOS S3TyLy4SYdPUmv5qXasDX4XkUrvPMfkMSROoG8KwvCFwnO/4wGz3duyYqtoJPTlI2rpI iMdw== X-Gm-Message-State: ALQs6tBQaJSmzjFlUR6Cm3OM8LJzPQIeWEpNzy64mcSkPmMlpFZde8Dn 9Phx3MZ3H7yRIYx4j/F6zmOZDw== X-Google-Smtp-Source: AB8JxZp91FG1HGr2dTlzua74UoWpeogfAaE2+AfO8HWzss++9j4s38/DR8GbDF3P3KVonU0GYOjFAQ== X-Received: by 2002:a6b:d90e:: with SMTP id r14-v6mr524920ioc.240.1524797778337; Thu, 26 Apr 2018 19:56:18 -0700 (PDT) Received: from [10.44.10.6] (ip-81-230-239-173.toronto.ca.northamericancoax.com. [173.239.230.81]) by smtp.googlemail.com with ESMTPSA id e94-v6sm584952itd.3.2018.04.26.19.56.16 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 26 Apr 2018 19:56:17 -0700 (PDT) To: "pgsql-admin@postgresql.org" From: Ron Subject: pg_restore dumps all data to the terminal Message-ID: <64dded41-6355-683c-a9f6-9253cbefd4c7@gmail.com> Date: Thu, 26 Apr 2018 21:56:15 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------AC44AE0356E043AA5D86F60A" Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk This is a multi-part message in MIME format. --------------AC44AE0356E043AA5D86F60A Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Hi, v9.6.8, restoring from 8.4.17 This command dumps not just the schema to the terminal (technically, nohup.out) but the actual data.  How do I stop that?  There's no --quiet, and that's not what I want anyway... pg_restore -cC --if-exists -e -Fd -j4 ${SOURCE}/${DB} "pg_dump --verbose"lists each object as it is backed up, and that's what I was expecting pg_restore to do. Thanks -- Angular momentum makes the world go 'round. --------------AC44AE0356E043AA5D86F60A Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit Hi,

v9.6.8, restoring from 8.4.17

This command dumps not just the schema to the terminal (technically, nohup.out) but the actual data.  How do I stop that?  There's no --quiet, and that's not what I want anyway...

pg_restore -cC --if-exists -e -Fd -j4 ${SOURCE}/${DB}

"pg_dump --verbose" lists each object as it is backed up, and that's what I was expecting pg_restore to do.

Thanks

--
Angular momentum makes the world go 'round.
--------------AC44AE0356E043AA5D86F60A--