| From: | Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com> |
|---|---|
| To: | Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> |
| Cc: | cktan(at)vitessedata(dot)com, 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 12:33:05 |
| Message-ID: | CAB=Je-EA22QdD_VJnnZY-f4pD5M5HVGMrJGUXym8E2Kfq=Er-g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> 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 identify updates made from a pl/pgsql procedure?
Vladimir
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Etsuro Fujita | 2018-05-11 12:46:05 | Re: postgres_fdw: Oddity in pushing down inherited UPDATE/DELETE joins to remote servers |
| Previous Message | Tatsuo Ishii | 2018-05-11 12:26:42 | Re: Having query cache in core |