| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Marko Tiikkaja <marko(at)joh(dot)to> |
| Cc: | Joel Jacobson <joel(at)compiler(dot)org>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: security_definer_search_path GUC |
| Date: | 2021-06-02 19:20:11 |
| Message-ID: | 202106021920.fsc7tn3wjhzz@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2021-Jun-02, Marko Tiikkaja wrote:
> The use case is: version upgrades. I want to be able to have a search_path
> of something like 'pg_catalog, compat, public'. That way we can provide
> compatibility versions of newer functions in the "compat" schema, which get
> taken over by pg_catalog when running on a newer version. That way all the
> compatibility crap is clearly separated from the stuff that should be in
> "public".
Can't you achieve that with "ALTER DATABASE .. SET search_path"?
--
Álvaro Herrera Valdivia, Chile
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2021-06-02 19:43:46 | Re: TAP tests still sensitive to various PG* environment variables |
| Previous Message | Alvaro Herrera | 2021-06-02 19:08:44 | Re: Support for CREATE MODULE? |