| From: | Euler Taveira <euler(at)timbira(dot)com(dot)br> |
|---|---|
| To: | Tim Burgan <timburgan(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: user-based query white list |
| Date: | 2017-07-03 13:23:27 |
| Message-ID: | CAHE3wgg7s_Z7Tg9UM+s2sACL75AMQVwA17qg1z6bwtmenf_kSw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2017-07-03 3:11 GMT-03:00 Tim Burgan <timburgan(at)gmail(dot)com>:
>
> Since then, is it now possible to configure a user to only be able to
> execute a limited white-listing of queries? Is this something that could
> now be implemented through extensions?
>
Since pg_stat_statements infrastructure, it is possible to create
extensions that prohibit query execution for certain users (see
sql_firewall [1] as an example).
[1] https://github.com/uptimejp/sql_firewall
--
Euler Taveira Timbira -
http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
<http://www.timbira.com.br>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2017-07-03 13:39:38 | Re: AdvanceXLInsertBuffer vs. WAL segment compressibility |
| Previous Message | Michael Paquier | 2017-07-03 13:21:51 | Re: WIP patch for avoiding duplicate initdb runs during "make check" |