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 1g4WZM-0001dO-0a for pgsql-performance@arkaria.postgresql.org; Mon, 24 Sep 2018 19:30:56 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1g4WZK-0005Ki-B6 for pgsql-performance@arkaria.postgresql.org; Mon, 24 Sep 2018 19:30:54 +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 1g4WZJ-0005KT-Vz for pgsql-performance@lists.postgresql.org; Mon, 24 Sep 2018 19:30:54 +0000 Received: from mail-it1-x141.google.com ([2607:f8b0:4864:20::141]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1g4WZG-0003PR-0q for pgsql-performance@postgresql.org; Mon, 24 Sep 2018 19:30:53 +0000 Received: by mail-it1-x141.google.com with SMTP id c85-v6so3393547itd.1 for ; Mon, 24 Sep 2018 12:30:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=OMj1BPnu5U4R/4+WQJpsuCGuygAe5g+WHSIsNNhyuW0=; b=KIYcZWSuS2LPs6ojkAwNoGZs3lcxdySVAi4hF3ztZnqmt6Q+BmVqJ6UwvG4Dhl/AGX uG/Y8kcLxAeLhhIW9mX86TWXH81uooztZjh0TdHn9jVLdjK+ew0tH/BOlsRAQsnZ5BOb Zhjq4VfZbJ3so4gfiDJMyiGdOGnTgaylNaRD8CQklMhB8orsPKACf4HCLyNAue7bC7hq CN0yPTEKiMcyynz4JdYVeUc9v5sai10SUgSvTkFcHEaVXBwGoSTAzUqByzwrjYZgpeiZ jyg/LfYhaB5w3p7AJ3ZlZhsokZhYFbZbIrq6dJm2YLtWalZBhpnyg5mZVITOa85C0OV2 ioWQ== 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:user-agent; bh=OMj1BPnu5U4R/4+WQJpsuCGuygAe5g+WHSIsNNhyuW0=; b=kJNFq6oDxADEejeDyl96+PEH54a2HUYeFBa8m6G8mcZFasRCH4+SsGT4btiAeHU6LL edwizpb6ADEWl3w5BvqhrQB9u/nlVcYBMC5HR6G6V3al5/LK/VIUDOA1WOlnlpUlbfev AyGDd79r7bedofla5YQbGZArCxkBvkORGQCjIRvi976JR2l3QjSnjBRq8YOF0vxxYO2N x2YkMtqYMs/3OMFSMebRWZM1pnPrtN/RYg7mOTvYQhY2C8juVAS/GH7xx9w4iBHVeMrt qMMWVpRztkf8TUZd68s9PB9ex3IjYeSQ9oN4nFqSc3V9n6paiL3URATmrnpuLfJMILYJ xf/A== X-Gm-Message-State: ABuFfojeIRMMN5OmSLOndROk2S8hrL20lqsTLsDIznLnqOXPnh8/UknG e0Li0SrDykkzwhWvQqdrkLg9lA== X-Google-Smtp-Source: ACcGV60Z6GqJLsiTHqB7dGLHr0bbWSPP9o4HxhSBEe1pAoaAPOfDasgfOokaTaPKumf/nZWaPiwh1g== X-Received: by 2002:a02:5c46:: with SMTP id q67-v6mr295685jab.85.1537817446313; Mon, 24 Sep 2018 12:30:46 -0700 (PDT) Received: from pryzbyj (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id r126-v6sm8865743ita.26.2018.09.24.12.30.45 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 24 Sep 2018 12:30:45 -0700 (PDT) Received: by pryzbyj (Postfix, from userid 1000) id E03568025FB; Mon, 24 Sep 2018 14:30:44 -0500 (CDT) Date: Mon, 24 Sep 2018 14:30:44 -0500 From: Justin Pryzby To: legrand legrand Cc: pgsql-performance@postgresql.org Subject: Re: Explain is slow with tables having many columns Message-ID: <20180924193044.GU2471@telsasoft.com> References: <1537816948278-0.post@n3.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1537816948278-0.post@n3.nabble.com> User-Agent: Mutt/1.5.23 (2014-03-12) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk 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