Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dJmmE-0001il-8g for pgsql-performance@arkaria.postgresql.org; Sat, 10 Jun 2017 20:14:30 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dJmmD-0003lr-LB for pgsql-performance@arkaria.postgresql.org; Sat, 10 Jun 2017 20:14:29 +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.84_2) (envelope-from ) id 1dJmkT-0000iR-VT for pgsql-performance@postgresql.org; Sat, 10 Jun 2017 20:12:42 +0000 Received: from mail-wr0-x22b.google.com ([2a00:1450:400c:c0c::22b]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1dJmkR-0002rn-41 for pgsql-performance@postgresql.org; Sat, 10 Jun 2017 20:12:41 +0000 Received: by mail-wr0-x22b.google.com with SMTP id q97so61553269wrb.2 for ; Sat, 10 Jun 2017 13:12:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:priority:user-agent; bh=PPgU/uKHQyhXLgSrOyGvAp7CZzV90qvW0w9C9kvxqy8=; b=rsGtjOFvWRxBI9uGgsPeiDdtBjIVjnzCzz4T9Zq2njsll+ppTYBgGvsnMy2TejdURt 7BlvvK6jjrsXdiAnCYAYxVvHY3Izm/sufBz2TardX1TI+Lci5fgfTGDeAnsg+DXV6vjs 4spPKIDixTXl4+tzVaNYe95bhE8j9JEdUNi1/qp/U8+WUXEcEEefVuRQ2Dbpx02f/S5r Xf96kUHefeLFFpcgCpprHj1Qu2GUugLkd83H/ht4xTru99iz8tHztgfHy3sN2Miicl5z k96mZ+nzADeOzm7VlsMTL1pppuAvJEowzSw8Cb3ld/xuvohR/23cznk8jVGtuncjcVps ATGw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:priority:user-agent; bh=PPgU/uKHQyhXLgSrOyGvAp7CZzV90qvW0w9C9kvxqy8=; b=dnfISS+qShdqHhfkYmUDjamxupRbL8fozh20P5bklwIHR+Upwls+rExMQNopFD34CF UsdFDrKTYA16A+F7/wihh82qZ0nO+yQf39V0qvDsKHnDVv6J6Qkx4PU7vSzbYKxOjPum F+1pxmuWoFAsUmZMUnIJNCa+moWPEVMt/bNLfGFldyET8UBnN4ix2HrmkZ+VGoiUhU5J eNPakOy48QH4QzdU5Y5E2h77v18UjIVRnrN6J9k+RVPc7WQaUkpY0nfAD2fmO2jpj/U0 Vq2S0y7p04hHqK3nhQheZUfzgNBEo4rl9jGKJSSoydbmHrs42ICpFqOHRRdp8ktceiRf qSNg== X-Gm-Message-State: AKS2vOzrXI1fic0j92SHFMK5MImivtfHDHPH3ggGtHgRBXtlcJaq8Led PRxCnFcyRk6AIg== X-Received: by 10.28.185.7 with SMTP id j7mr3590916wmf.74.1497125557080; Sat, 10 Jun 2017 13:12:37 -0700 (PDT) Received: from localhost (ip-16.net-81-220-6.versailles.rev.numericable.fr. [81.220.6.16]) by smtp.gmail.com with ESMTPSA id g3sm10125729wrd.11.2017.06.10.13.12.36 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 10 Jun 2017 13:12:36 -0700 (PDT) Date: Sat, 10 Jun 2017 22:12:35 +0200 From: Nicolas Paris To: Frits Jalvingh Cc: Scott Marlowe , Kenneth Marshall , Andreas Kretschmer , "pgsql-performance@postgresql.org" Subject: Re: Improving PostgreSQL insert performance Message-ID: <20170610201235.GA8502@gmail.com> References: <9e2a0a34-dd83-43af-d41a-791b34ff76e1@a-kretschmer.de> <20170609132857.GC26506@aart.rice.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org > I tried the copy command, and that indeed works quite brilliantly: > Inserted 24000000 rows in 22004 milliseconds, 1090710.7798582076 rows per > second > > That's faster than Oracle. But with a very bad interface I have to say for > normal database work.. I will try to make this work in the tooling, but it > needs some very special code to format all possible values properly, and to > manage the end of the copy, so it is not usable in general which is a pity, I > think. Have you thought about the COPY with binary format ? Thats looks more robust than the text format you used in your benchmarks. -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance