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 1g1W2S-00068c-SX for pgsql-performance@arkaria.postgresql.org; Sun, 16 Sep 2018 12:20:33 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1g1W2Q-0005Np-Gv for pgsql-performance@arkaria.postgresql.org; Sun, 16 Sep 2018 12:20:30 +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 1g1Pcl-00035s-EE for pgsql-performance@lists.postgresql.org; Sun, 16 Sep 2018 05:29:35 +0000 Received: from n3.nabble.com ([162.255.23.22]) by magus.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1g1Pcd-0007kJ-DU for pgsql-performance@postgresql.org; Sun, 16 Sep 2018 05:29:34 +0000 Received: from n3.nabble.com (localhost [127.0.0.1]) by n3.nabble.com (Postfix) with ESMTP id E228CF2BD8A7 for ; Sat, 15 Sep 2018 22:29:24 -0700 (MST) Date: Sat, 15 Sep 2018 22:29:24 -0700 (MST) From: padusuma To: pgsql-performance@postgresql.org Message-ID: <1537075764890-0.post@n3.nabble.com> In-Reply-To: <87k1nmgp58.fsf@gmail.com> References: <1536339842382-0.post@n3.nabble.com> <8736uk6eh5.fsf@gmail.com> <1536385261054-0.post@n3.nabble.com> <87zhwq48ap.fsf@gmail.com> <1536554876104-0.post@n3.nabble.com> <1536843459130-0.post@n3.nabble.com> <87tvmtvx4h.fsf@gmail.com> <1537030803688-0.post@n3.nabble.com> <87k1nmgp58.fsf@gmail.com> Subject: Re: Performance of INSERT into temporary tables using psqlODBC driver MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hello Tim, >Re-implementation of a solution is often a hard case to sell, but it >might be the only way to get the performance you want. The big positive >to a re-implementation is that you usually get a better solution because >you are implementing with more knowledge and experience about the >problem domain. Design is often cleaner and as a result, easier to >maintain. It usually takes a lot less time than the original >implementation as well and can be the more economical solution compared >to fighting a system which has fundamental design limitations that >restrict performance. Thank you for the suggestions and advice. I will definitely look into re-implementation of certain parts of our solution as an option to improve performance. -- Sent from: http://www.postgresql-archive.org/PostgreSQL-performance-f2050081.html