| From: | Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> |
|---|---|
| To: | hartmut(dot)holzgraefe(at)gmail(dot)com |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Having query cache in core |
| Date: | 2018-05-11 16:01:21 |
| Message-ID: | 20180512.010121.1210207641838286593.t-ishii@sraoss.co.jp |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> that's almost actually how the MySQL query cache works: the query
> cache
> lookup kicks in even before the query is parsed, to get maximum gain
> from cache hits.
>
> It does not just take the query text into account alone though,
> but also the current default database, protocol version,
> and character
> set/collation settings of the client session, asl all these may have
> an influence on the actual result values, too ...
Plus checking username is neccessary (otherwise any user could
retrieve a cache for a table lookup which is not permitted by other
users).
Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Pacheco | 2018-05-11 16:21:30 | Re: Compiler warnings with --enable-dtrace |
| Previous Message | CK Tan | 2018-05-11 16:00:18 | Re: Having query cache in core |