| From: | Michael Shapiro <mshapiro51(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: select view definition from pg_views feature request |
| Date: | 2019-11-04 13:48:50 |
| Message-ID: | CAGCvxeb63kt0yCOdGB2dkuEzvdKk33LQkAk-GawynMuc2SUnZw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Is that how PgAdmin does it? The views extracted by PgAdmin are fully
qualified....
On Sun, Nov 3, 2019 at 3:15 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Michael Shapiro <mshapiro51(at)gmail(dot)com> writes:
> > It seems that the definition of a view from pg_catalog.pg_views does not
> > qualify the tables used in the view if the tables are in the current
> search
> > path.
>
> > Is it possible to either have the definition always qualify all tables
> > independent of the search_path (or else provide a new column that does
> > that)?
>
> Why don't you just change the search path to empty before selecting?
>
> regards, tom lane
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-11-04 14:26:03 | Re: explain plan difference |
| Previous Message | Ashok Kumar Tiwari | 2019-11-04 13:35:24 | Create a logical and physical replication |