From: | Rod Taylor <rbt(at)zort(dot)ca> |
---|---|
To: | Alvaro Herrera <alvherre(at)atentus(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: current_schemas() |
Date: | 2002-09-07 18:58:08 |
Message-ID: | 1031425088.15580.7.camel@jester |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, 2002-09-07 at 14:39, Alvaro Herrera wrote:
> Hello,
>
> In http://developer.postgresql.org/docs/postgres/runtime-config.html,
> the SEARCH_PATH variable description mentions the use of
> current_schemas(), but this function doesn't exist (or it didn't exist
> last time I updated:
> #define CATALOG_VERSION_NO 200209021
> )
>
> What exists is current_schema(), but it doesn't expand to the full
> search path; apparently, only the first item that exists:
>
> testing=# set search_path to '$user', 'public', 'alvh1', 'alvh2';
> SET
> testing=# select current_schema();
> current_schema
> ----------------
> public
> (1 row)
Heres what I get. Note current_schemas() shows the full search path,
where current_schema() shows only the first.
a=# set search_path to k,l;
SET
a=# select current_schemas(true);
current_schemas
------------------
{pg_catalog,k,l}
(1 row)
From | Date | Subject | |
---|---|---|---|
Next Message | Hervé Piedvache | 2002-09-07 19:03:47 | Impossible to import pg_dumpall from 7.2.2 to 7.3b1 |
Previous Message | snpe | 2002-09-07 18:57:55 | Re: [JDBC] problem with new autocommit config parameter and jdbc |