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.92) (envelope-from ) id 1jG5uG-0002wG-QG for pgsql-docs@arkaria.postgresql.org; Sun, 22 Mar 2020 19:05:08 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1jG5uF-0002Pq-I5 for pgsql-docs@arkaria.postgresql.org; Sun, 22 Mar 2020 19:05:07 +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 1jG5uF-0002Pj-6x for pgsql-docs@lists.postgresql.org; Sun, 22 Mar 2020 19:05:07 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jG5uC-0000z7-5t for pgsql-docs@lists.postgresql.org; Sun, 22 Mar 2020 19:05:06 +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 02MJ51ur022708; Sun, 22 Mar 2020 15:05:02 -0400 From: Tom Lane To: Bruce Momjian cc: protodef@gmail.com, pgsql-docs@lists.postgresql.org Subject: Re: optionally schema-qualified for table_name In-reply-to: <20200322001310.GA2031@momjian.us> References: <158399268229.5708.13296960177949398026@wrigleys.postgresql.org> <20200322001310.GA2031@momjian.us> Comments: In-reply-to Bruce Momjian message dated "Sat, 21 Mar 2020 20:13:10 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <22706.1584903901.1@sss.pgh.pa.us> Date: Sun, 22 Mar 2020 15:05:01 -0400 Message-ID: <22707.1584903901@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Bruce Momjian writes: > I see what you mean. The attached patch fixes this, as well as > adjusting the error message. I didn't see any other cases. I don't really think this is an improvement, mainly because that error message is inventing a notation that we do not use in any other error message. regards, tom lane