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 1g4Wls-00027S-EK for pgsql-performance@arkaria.postgresql.org; Mon, 24 Sep 2018 19:43:52 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1g4Wlq-0001Gp-Nw for pgsql-performance@arkaria.postgresql.org; Mon, 24 Sep 2018 19:43:50 +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 1g4Wlq-0001Gi-Gc for pgsql-performance@lists.postgresql.org; Mon, 24 Sep 2018 19:43:50 +0000 Received: from n3.nabble.com ([162.255.23.22]) by magus.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1g4Wlm-0003fo-N2 for pgsql-performance@postgresql.org; Mon, 24 Sep 2018 19:43:49 +0000 Received: from n3.nabble.com (localhost [127.0.0.1]) by n3.nabble.com (Postfix) with ESMTP id 722CFF55ED1B for ; Mon, 24 Sep 2018 12:43:44 -0700 (MST) Date: Mon, 24 Sep 2018 12:43:44 -0700 (MST) From: legrand legrand To: pgsql-performance@postgresql.org Message-ID: <1537818224423-0.post@n3.nabble.com> In-Reply-To: <20180924193044.GU2471@telsasoft.com> References: <1537816948278-0.post@n3.nabble.com> <20180924193044.GU2471@telsasoft.com> Subject: Re: Explain is slow with tables having many columns 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 Justin Pryzby wrote > On Mon, Sep 24, 2018 at 12:22:28PM -0700, legrand legrand wrote: >> Hello, >> I have found that explain on tables with many (hundreds) columns >> are slow compare to nominal executions. > > See also this thread from last month: > > https://www.postgresql.org/message-id/flat/CAEe%3DmRnNNL3RDKJDmY%3D_mpcpAb5ugYL9NcchELa6Qgtoz2NjCw%40mail.gmail.com > > Justin maybe, I will check that patch ... I thought it would also have been related to https://www.postgresql.org/message-id/CAMkU%3D1xPqHP%3D7YPeChq6n1v_qd4WGf%2BZvtnR-b%2BgyzFqtJqMMQ%40mail.gmail.com Regards PAscal -- Sent from: http://www.postgresql-archive.org/PostgreSQL-performance-f2050081.html