> On Feb 18, 2023, at 06:59, Peter J. Holzer <hjp-pg...@hjp.at> wrote: > I think the reason > is that the use case (the exact same query is submitted repeatedly) is > sufficiently rare that it isn't all that effective in practice. And, in this use case, a prepared statement is in effect a cache of the parsing and planning of the query. Detecting identical queries and caching their results while maintaining good invalidation is a much harder problem.
- Re: Does Postgres 14 have a query cache? Peter J. Holzer
- Re: Does Postgres 14 have a query cache? Christophe Pettus
- Re: Does Postgres 14 have a query cache? Steven Lembark
- Re: Does Postgres 14 have a query cache? Siddharth Jain
- Re: Does Postgres 14 have a query cache? Tatsuo Ishii