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 1gHTub-0001m3-LR for pgsql-admin@arkaria.postgresql.org; Tue, 30 Oct 2018 13:18:25 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gHTuZ-0007VR-Nn for pgsql-admin@arkaria.postgresql.org; Tue, 30 Oct 2018 13:18:23 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1gHTuZ-0007VI-CJ for pgsql-admin@lists.postgresql.org; Tue, 30 Oct 2018 13:18:23 +0000 Received: from mx2.mailbox.org ([80.241.60.215]) by makus.postgresql.org with esmtps (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gHTuV-0008Hq-UT for pgsql-admin@postgresql.org; Tue, 30 Oct 2018 13:18:21 +0000 Received: from smtp2.mailbox.org (unknown [IPv6:2001:67c:2050:105:465:1:2:0]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)) (No client certificate requested) by mx2.mailbox.org (Postfix) with ESMTPS id AFC06A1197; Tue, 30 Oct 2018 14:18:15 +0100 (CET) X-Virus-Scanned: amavisd-new at heinlein-support.de Received: from smtp2.mailbox.org ([80.241.60.241]) by spamfilter04.heinlein-hosting.de (spamfilter04.heinlein-hosting.de [80.241.56.122]) (amavisd-new, port 10030) with ESMTP id md8O6cr65MuV; Tue, 30 Oct 2018 14:18:13 +0100 (CET) Message-ID: <31055688b81895792fa7d8c61e07dca7add3dbb9.camel@cybertec.at> Subject: Re: Getting fancy errors when accessing information_schema on 10.5 From: Laurenz Albe To: Tom Lane , Axel Rau Cc: pgsql-admin@postgresql.org Date: Tue, 30 Oct 2018 14:18:12 +0100 In-Reply-To: <20191.1540901834@sss.pgh.pa.us> References: <4880e067723cefc1dc2e08a117f96de26ae0f797.camel@cybertec.at> <44D4C7B1-0DCF-4166-9DB8-B5D75EB2985E@Chaos1.DE> <20191.1540901834@sss.pgh.pa.us> Organization: Cybertec Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Tom Lane wrote: > It doesn't happen for me either. Looking at the planner code, it seems > like the relkind check should happen first because it'd be cheaper than > the OR condition. It is still unclear why the execution plan looks like that, but maybe it would be more robust to change "has_sequence_privilege" so that it just returns FALSE if the argument is not a sequence. Yours, Laurenz Albe