| From: | Marko Tiikkaja <marko(at)joh(dot)to> |
|---|---|
| To: | Joel Jacobson <joel(at)compiler(dot)org> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: security_definer_search_path GUC |
| Date: | 2021-05-29 20:10:44 |
| Message-ID: | CAL9smLDPFRn0kqpJRK8XCt_fXA_HNRN9Z9b5hg2iQAt9coPnHA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, May 29, 2021 at 11:06 PM Joel Jacobson <joel(at)compiler(dot)org> wrote:
> Glad you bring this problem up for discussion, something should be done to
> improve the situation.
>
> Personally, as I really dislike search_path and consider using it an
> anti-pattern.
> I would rather prefer a GUC to hard-code search_path to a constant default
> value of just ‘public’ that cannot be changed by anyone or any function.
> Trying to change it to a different value would raise an exception.
>
That would work, too! I think it's a nice idea, perhaps even better than
what I proposed. I would be happy to see either one incorporated.
.m
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dean Gibson (DB Administrator) | 2021-05-29 20:17:40 | Re: AWS forcing PG upgrade from v9.6 a disaster |
| Previous Message | Joel Jacobson | 2021-05-29 20:05:34 | Re: security_definer_search_path GUC |