Date: Sun, 22 Mar 2020 21:27:57 -0400
From: Bruce Momjian <bruce@momjian.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: protodef@gmail.com, pgsql-docs@lists.postgresql.org
Subject: Re: optionally schema-qualified for table_name
Message-ID: <20200323012757.GC2031@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>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4628.1584915604@sss.pgh.pa.us>
User-Agent: Mutt/1.10.1 (2018-07-13)
Precedence: bulk

On Sun, Mar 22, 2020 at 06:20:04PM -0400, Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> 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.

-- 
  Bruce Momjian  <bruce@momjian.us>        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 +