| 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>, Tom Lane <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 22:20:13 |
| Message-ID: | CAJNt7=b+GsmV7Q30t4UAG6jd7igk3uKK=16CY39nFmPhfSTEkQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, May 12, 2018 at 8:18 AM, Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> wrote:
> >
> > 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?
>
> Pgpool-II do not invalidate cache entries for views, triggers and
> others. That's an limitation of the implementation in Pgpool-II.
>
> I think in-core query cache would not have the limitation because it
> would have a full access to system catalogs and wal.
>
>
Yes. That's my point. You can't do it outside the core.
-cktan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2018-05-11 22:32:04 | Re: Having query cache in core |
| Previous Message | Tatsuo Ishii | 2018-05-11 22:18:30 | Re: Having query cache in core |