On 07.05.2018 11:24, Tsunakawa, Takayuki wrote:
From: Konstantin Knizhnik [mailto:k.knizh...@postgrespro.ru]
But I think it is better to start first with
1. Global prepared statements cache
2. Global catalog cache
3. Global relation cache
May I ask why prepared statements need to precede catalog and relation caches?
We're suffering from the bloat of catalog and relation caches, and are thinking
of proposing placing those caches in shared memory.
Sorry, I didn't assume some particular order here. Yes, shared catalog
and relation cache seems to be more important to implement first.
Switch to global caches seems to be a challenged task, requiring a lot
of changes in Postgres core.
But I think that sometime we will have to implement them in any case (as
it was done in most of other DBMSes).
Agreed. I respect your attitude toward revolutionizing PostgreSQL.
Concerning result cache, I think it will be better to ask opinion of
mysql users: how useful it is.
And possibly Oracle Database users, as Oracle implemented it relatively
recently, IIRC.
Regards
Takayuki Tsunakawa
--
Konstantin Knizhnik
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
