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 1jH5U6-0003dG-3W for pgsql-docs@arkaria.postgresql.org; Wed, 25 Mar 2020 12:50:14 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1jH5U4-0004iG-Up for pgsql-docs@arkaria.postgresql.org; Wed, 25 Mar 2020 12:50:12 +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 1jH5R2-0000ib-81 for pgsql-docs@lists.postgresql.org; Wed, 25 Mar 2020 12:47:04 +0000 Received: from out3-smtp.messagingengine.com ([66.111.4.27]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jH5Qy-0000dN-7P for pgsql-docs@lists.postgresql.org; Wed, 25 Mar 2020 12:47:03 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id D50095C01A1; Wed, 25 Mar 2020 08:46:57 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Wed, 25 Mar 2020 08:46:57 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=uvqkTJTrgxYj/vUdkL5+uy/F2h1+DlwRJHnXrNso2 9k=; b=CNva2leyZ5RVNCqn7cYOM4v07OHCQtDiMa/f0XyKtgcjGc6UASXt3F4Uu LPWbsf82AsaNzKOLKYJTh9REuwnXJ/MJ8VGbhw2V+r5hTIb+nXhVHC/qShNaHOSx D5Q93qdofaPHipB4pvTLR+JMJlsnypMpSxWno4fhOIp5A9xBTfKWlCHFaksP2ome yKDK25Zrzmbc6qKHqCVQ9Ft62ZMTKVxveWluRstbwPRnawaoEH7SP6yjQrUub48M 30XIK3qCc9xSm8e6LIdpEX1RLn0PPmty1AH7mSHYF31JW2/pqJv2i0si9fPvmASn FCUYO5vorNkcoa5cQYUrVchZtqOnA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedrudehgedgudelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepuffvfhfhohfkffgfgggjtgfgsehtjeertddtfeejnecuhfhrohhmpefrvght vghrucfgihhsvghnthhrrghuthcuoehpvghtvghrrdgvihhsvghnthhrrghuthesvdhnug hquhgrughrrghnthdrtghomheqnecuffhomhgrihhnpedvnhguqhhurggurhgrnhhtrdgt ohhmnecukfhppeelfedrvdegvddrvddufedrvdegudenucevlhhushhtvghrufhiiigvpe dtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehpvghtvghrrdgvihhsvghnthhrrghuthes vdhnughquhgrughrrghnthdrtghomh X-ME-Proxy: Received: from april.pezone.net (p5df2d5f1.dip0.t-ipconnect.de [93.242.213.241]) by mail.messagingengine.com (Postfix) with ESMTPA id AC82F306617D; Wed, 25 Mar 2020 08:46:56 -0400 (EDT) Subject: Re: optionally schema-qualified for table_name To: Bruce Momjian 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> <20200324205818.GA32258@momjian.us> Cc: Tom Lane , protodef@gmail.com, pgsql-docs@lists.postgresql.org From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: <4b09907d-96de-c1da-34cd-787877503385@2ndquadrant.com> Date: Wed, 25 Mar 2020 13:46:54 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <20200324205818.GA32258@momjian.us> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2020-03-24 21:58, Bruce Momjian wrote: > 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. The CREATE RECURSIVE VIEW example is making a specific point about schema qualification, which is explained below the example. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services