| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| 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 12:46:54 |
| Message-ID: | 4b09907d-96de-c1da-34cd-787877503385@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
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.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2020-03-25 20:10:54 | Re: optionally schema-qualified for table_name |
| Previous Message | Bruce Momjian | 2020-03-24 20:58:18 | Re: optionally schema-qualified for table_name |