Re: Does Postgres 14 have a query cache?

From: Christophe Pettus <xof(at)thebuild(dot)com>
To: PostgreSQL <pgsql-general(at)lists(dot)postgresql(dot)org>
Cc: "Peter J(dot) Holzer" <hjp-pgsql(at)hjp(dot)at>
Subject: Re: Does Postgres 14 have a query cache?
Date: 2023-02-18 16:08:14
Message-ID: 06C7D8B6-A577-411A-8754-63D18C6360B4@thebuild.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> On Feb 18, 2023, at 06:59, Peter J. Holzer <hjp-pgsql(at)hjp(dot)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.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Erik Wienhold 2023-02-18 16:16:12 Re: can't get psql authentication against Active Directory working
Previous Message Peter J. Holzer 2023-02-18 14:59:20 Re: Does Postgres 14 have a query cache?