This is the official mirror of git://git.postgresql.org/git/pgpool2.git. Note that this is just a *mirror* - we don't work with pull requests on github. Please subscribe to pgpool-hackers mailing list from our website and submit your patch to this mailing list.
I can confirm that the queries are actually being cached.
The problem is that the cache would not invalidate even after updates, inserts and deletes on the same table. That is what happens:
Select a row from table - cache is not present - actual select is performed.
Select the same row - row is retrieved from cache.
Update the same row - success.
Select the same row - row is retrieved from cache.
Cache invalidation works as expected in public schema but not in other schemas. I've read this in FAQ:
When I use schema qualified table names, pgpool-II does not invalidate
on memory query cache and I got outdated data. Why? It seems you did
not install "pgpool_regclass" function. Without the function,
pgpool-II ignores the schema name pat of the schema qualified table
name and the cache invalidation fails.
I've installed both pgpool_adm, pgpool_recovery and pgpool_regclass extensions both on the application and postgres databases but cache is still not invalidating.
Can someone confirm the issue or am I doing something wrong?
I've configured
pgpool2
(v3.4.3) withpostgresql
(v9.5) to cache queries like this:I can confirm that the queries are actually being cached.
The problem is that the cache would not invalidate even after updates, inserts and deletes on the same table. That is what happens:
Cache invalidation works as expected in
public
schema but not in other schemas. I've read this in FAQ:I've installed both
pgpool_adm
,pgpool_recovery
andpgpool_regclass
extensions both on theapplication
andpostgres
databases but cache is still not invalidating.Can someone confirm the issue or am I doing something wrong?