| From: | Hartmut Holzgraefe <hartmut(dot)holzgraefe(at)gmail(dot)com> |
|---|---|
| To: | Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Having query cache in core |
| Date: | 2018-05-11 16:31:15 |
| Message-ID: | eea522dc-8350-6eb2-2883-42660cc8d6df@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 11.05.2018 18:01, Tatsuo Ishii wrote:
> Plus checking username is neccessary (otherwise any user could
> retrieve a cache for a table lookup which is not permitted by other
> users).
as the tables a cached query operated on is known anyway -- it's needed
to purge cache entries when table content changes -- schema and table
level SELECT privileges can be checked ... I'm not fully sure about
how MySQL handles its column level privileges in that respect, something
I'd need to try out ...
--
hartmut
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Teodor Sigaev | 2018-05-11 16:49:50 | Re: Postgres 11 release notes |
| Previous Message | Fabien COELHO | 2018-05-11 16:29:39 | Re: Postgres 11 release notes |