current_schemas() - Mailing list pgsql-hackers

From Alvaro Herrera
Subject current_schemas()
Date
Msg-id Pine.LNX.4.44.0209071435250.7189-100000@cm-lcon1-46-187.cm.vtr.net
Whole thread Raw
Responses Re: current_schemas()
List pgsql-hackers
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)

This is not good:

testing=# \d foo     Table "alvh1.foo"Column |  Type   | Modifiers 
--------+---------+-----------a      | integer | not null
Indexes: foo_pkey primary key btree (a)

(and alvh1 does not appear on current_schema)

Is this a bug?

-- 
Alvaro Herrera (<alvherre[a]atentus.com>)
"Como puedes confiar en algo que pagas y que no ves,
y no confiar en algo que te dan y te lo muestran?" (German Poo)



pgsql-hackers by date:

Previous
From: snpe
Date:
Subject: Re: [JDBC] problem with new autocommit config parameter and jdbc
Next
From: Rod Taylor
Date:
Subject: Re: current_schemas()