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 1jGqd2-00017v-C6 for pgsql-docs@arkaria.postgresql.org; Tue, 24 Mar 2020 20:58:28 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1jGqcz-0001yZ-T6 for pgsql-docs@arkaria.postgresql.org; Tue, 24 Mar 2020 20:58:25 +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 1jGqcz-0001yS-LN for pgsql-docs@lists.postgresql.org; Tue, 24 Mar 2020 20:58:25 +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 1jGqcv-0008Gl-Gq for pgsql-docs@lists.postgresql.org; Tue, 24 Mar 2020 20:58:23 +0000 Received: from bruce by momjian.us with local (Exim 4.92) (envelope-from ) id 1jGqcs-0003Bv-Jh; Tue, 24 Mar 2020 16:58:18 -0400 Date: Tue, 24 Mar 2020 16:58:18 -0400 From: Bruce Momjian To: Peter Eisentraut Cc: Tom Lane , protodef@gmail.com, pgsql-docs@lists.postgresql.org Subject: Re: optionally schema-qualified for table_name Message-ID: <20200324205818.GA32258@momjian.us> References: <158399268229.5708.13296960177949398026@wrigleys.postgresql.org> <20200322001310.GA2031@momjian.us> <22707.1584903901@sss.pgh.pa.us> <20200322201518.GB2031@momjian.us> <4628.1584915604@sss.pgh.pa.us> <20200323012757.GC2031@momjian.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Tue, Mar 24, 2020 at 09:35:25PM +0100, Peter Eisentraut wrote: > On 2020-03-23 02:27, Bruce Momjian wrote: > > On Sun, Mar 22, 2020 at 06:20:04PM -0400, Tom Lane wrote: > > > Bruce Momjian writes: > > > > On Sun, Mar 22, 2020 at 03:05:01PM -0400, Tom Lane wrote: > > > > > 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. > > > > > > Yeah, and I think that's okay as-is, or at least we can't make it better > > > without fairly whole-sale changes of our documentation practices. > > > The fact that a table name can be schema-qualified is usually implicit, > > > and I don't see why this place cries out for making it explicit > > > more than other places. You could as well complain that there's > > > nothing explicit here about double-quoting practices. > > > > OK, I will do just the documentation patch for this then. > > The same criticism applies to the documentation patch, I think. We don't > usually make the schema part explicit. That is a good point. I used CREATE VIEW as an example because that is what the user reported, but it seems only create_view and reindexed use a schema name qualification: $ grep -l 'schema' *.sgml create_view.sgml reindexdb.sgml The reindexdb use is because of -S (reindex schema), which makes sense. The create view case is used in an example of CREATE RECURSIVE VIEW and should probably be removed. -- 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 +