| From: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> |
|---|---|
| To: | George Neuner <gneuner2(at)comcast(dot)net> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: select view definition from pg_views feature request |
| Date: | 2019-11-05 01:29:00 |
| Message-ID: | CAKJS1f9S0JOoE0CVzrrrumYzBvTSGKx3rct+rvjscdurwJ_frA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, 5 Nov 2019 at 11:05, George Neuner <gneuner2(at)comcast(dot)net> wrote:
>
> On Sun, 03 Nov 2019 16:15:23 -0500, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
> >Why don't you just change the search path to empty before selecting?
>
>
> I'm guessing this is fine inside a transaction, but what if you're
> using a client that commits by statement? In that case, wouldn't the
> change to the path affect the other backends?
See https://www.postgresql.org/docs/current/sql-set.html
"SET only affects the value used by the current session."
Also:
"The effects of SET LOCAL last only till the end of the current transaction"
Neither affects other sessions.
--
David Rowley http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro Horiguchi | 2019-11-05 05:54:41 | Re: Create a logical and physical replication |
| Previous Message | George Neuner | 2019-11-04 22:05:11 | Re: select view definition from pg_views feature request |