Re: Having query cache in core - Mailing list pgsql-hackers

From CK Tan
Subject Re: Having query cache in core
Date
Msg-id CAJNt7=YWSMTW7eZr-UzDP3i7EnFUE0yTkWcE4kSjoFtVq_S9gw@mail.gmail.com
Whole thread Raw
In response to Re: Having query cache in core  (Tatsuo Ishii <ishii@sraoss.co.jp>)
Responses Re: Having query cache in core  (Tatsuo Ishii <ishii@sraoss.co.jp>)
List pgsql-hackers


On Fri, May 11, 2018, 10:26 PM Tatsuo Ishii <ishii@sraoss.co.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

pgsql-hackers by date:

Previous
From: Tatsuo Ishii
Date:
Subject: Re: Having query cache in core
Next
From: Tatsuo Ishii
Date:
Subject: Re: Having query cache in core