| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, protodef(at)gmail(dot)com, pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: optionally schema-qualified for table_name |
| Date: | 2020-03-25 20:10:54 |
| Message-ID: | 20200325201054.GA27957@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Wed, Mar 25, 2020 at 01:46:54PM +0100, Peter Eisentraut wrote:
> 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 '<replaceable>schema</replaceable>' *.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.
OK, so I guess everything is fine and we can just go back to other
business. :-) Sorry for the distraction.
--
Bruce Momjian <bruce(at)momjian(dot)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 +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Brett Okken | 2020-03-26 11:34:24 | char 0x00 |
| Previous Message | Peter Eisentraut | 2020-03-25 12:46:54 | Re: optionally schema-qualified for table_name |