| From: | CK Tan <cktan(at)vitessedata(dot)com> |
|---|---|
| To: | Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> |
| Cc: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, tgl(at)sss(dot)pgh(dot)pa(dot)us, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Having query cache in core |
| Date: | 2018-05-11 16:00:18 |
| Message-ID: | CAJNt7=YWSMTW7eZr-UzDP3i7EnFUE0yTkWcE4kSjoFtVq_S9gw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, May 11, 2018, 10:26 PM Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> wrote:
>
> >
> > I think you need to know which tables are involved and if they were
> > modified.
>
> Of course. While creating a cache entry for a SELECT, we need to
> analyze it and extract tables involved in the SELECT. The information
> should be stored along with the cache entry. If any of the tables were
> modified, cache entries using the table must be removed.
> (these are already implemented in Pgpool-II's in memory query cache)
>
How do you handle tables hiding behind views? Also how does cached entries
in pgpools know if some tables are modified without going thru pgpool, eg
pgplsql or trigger or via psql directly?
=cktan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2018-05-11 16:01:21 | Re: Having query cache in core |
| Previous Message | Tatsuo Ishii | 2018-05-11 15:55:35 | Re: Having query cache in core |