Re: Search path in connection string

Can this be considered?

I have a use case where there doesn't appear to be any good alternatives: using BIRT, with multiple clients sharing a Postgres database with one schema each, one cannot just execute a SET SCHEMA statement (UPDATE pg_settings ... is not possible either) and qualifying object names is also not always possible (say, if there are stored procedures involved that use unqualified object names).

Besides being useful in this case and surely others, this feature makes sense: schemas can be used to offer separation of database objects very similar to that offered by having multiple databases, and the database itself is part of the connection string.

The patch proposed in http://postgresql.1045698.n5.nabble.com/Patch-to-allow-setting-schema-search-path-in-the-connectionURL-td2174512.html is still applicable.

Regards,

Julien

You can customize the connection string to accomplish this.  You vary the “user” that is connecting and configure a search_path specific to that user.

ALTER ROLE custom_role SET search_path = …

David J.