| From: | Michael Fuhr <mike(at)fuhr(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "D(dot)J(dot) Kniep" <dick(dot)kniep(at)lindix(dot)nl>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #1858: setting search path in select doesn't (always) work |
| Date: | 2005-09-02 15:12:50 |
| Message-ID: | 20050902151250.GA66056@winnie.fuhr.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Sep 02, 2005 at 10:58:12AM -0400, Tom Lane wrote:
> "D.J. Kniep" <dick(dot)kniep(at)lindix(dot)nl> writes:
> > After setting the search path the query
> > Select * from vwexternetoegang
> > produces the required results in the first installation, but in the new
> > installation, it cannot find the view. However, if I do an explicit
> > Set search_path to "testschema";
> > it works as expected.
>
> What does "show search_path" report in the failing and non-failing states?
> Also try "select current_schemas(true)".
This thread came up in pgsql-general yesterday; Dick says the real
problem was something else.
http://archives.postgresql.org/pgsql-general/2005-09/msg00074.php
--
Michael Fuhr
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Turn Jensen | 2005-09-03 01:06:55 | BUG #1861: Possible Incompatibly with NOD32 AV. |
| Previous Message | Tom Lane | 2005-09-02 14:58:12 | Re: BUG #1858: setting search path in select doesn't (always) work |