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 1jG70J-0006CL-LR for pgsql-docs@arkaria.postgresql.org; Sun, 22 Mar 2020 20:15:27 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1jG70G-0008OF-QU for pgsql-docs@arkaria.postgresql.org; Sun, 22 Mar 2020 20:15:24 +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_SHA1:256) (Exim 4.89) (envelope-from ) id 1jG70G-0008O7-Ik for pgsql-docs@lists.postgresql.org; Sun, 22 Mar 2020 20:15:24 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jG70D-00008b-QP for pgsql-docs@lists.postgresql.org; Sun, 22 Mar 2020 20:15:24 +0000 Received: from bruce by momjian.us with local (Exim 4.92) (envelope-from ) id 1jG70B-0002qY-0Z; Sun, 22 Mar 2020 16:15:19 -0400 Date: Sun, 22 Mar 2020 16:15:18 -0400 From: Bruce Momjian To: Tom Lane Cc: protodef@gmail.com, pgsql-docs@lists.postgresql.org Subject: Re: optionally schema-qualified for table_name Message-ID: <20200322201518.GB2031@momjian.us> References: <158399268229.5708.13296960177949398026@wrigleys.postgresql.org> <20200322001310.GA2031@momjian.us> <22707.1584903901@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <22707.1584903901@sss.pgh.pa.us> User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Sun, Mar 22, 2020 at 03:05:01PM -0400, Tom Lane wrote: > 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. What do you suggest? The current message is: Specify OWNED BY table.column or OWNED BY NONE. I don't see any other messages with "table.column". Do you want? Specify OWNED BY column or OWNED BY NONE. -- Bruce Momjian https://momjian.us EnterpriseDB https://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription +