Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hO5iI-00023s-Ve for pgsql-hackers@arkaria.postgresql.org; Tue, 07 May 2019 19:25:19 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hO5iH-0002Ur-4F for pgsql-hackers@arkaria.postgresql.org; Tue, 07 May 2019 19:25:17 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hO5iG-0002RH-OX for pgsql-hackers@lists.postgresql.org; Tue, 07 May 2019 19:25:16 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hO5iE-0003Cx-FF for pgsql-hackers@lists.postgresql.org; Tue, 07 May 2019 19:25:15 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id x47JPB4w015151; Tue, 7 May 2019 15:25:11 -0400 From: Tom Lane To: Peter Eisentraut cc: pgsql-hackers@lists.postgresql.org Subject: Fuzzy thinking in is_publishable_class MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <15149.1557257111.1@sss.pgh.pa.us> Date: Tue, 07 May 2019 15:25:11 -0400 Message-ID: <15150.1557257111@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk is_publishable_class has a test "relid >= FirstNormalObjectId", which I think we should drop, for two reasons: 1. It makes the comment claiming that this function tests the same things as check_publication_add_relation a lie. 2. The comment about it claims that the purpose is to reject information_schema relations, but if that's so, it's ineffective. We consider it supported to drop and recreate information_schema, and have indeed recommended doing so for some minor-version upgrades. After that, the information_schema relations would no longer have OIDs recognizable to this test. So what is the motivation for this test? If there's an important reason for it, we need to find a less fragile way to express it. regards, tom lane