Re: Support prepared statement invalidation when result types change

From: Shay Rojansky <roji(at)roji(dot)org>
To: Jelte Fennema-Nio <me(at)jeltef(dot)nl>
Cc: Andy Fan <zhihui(dot)fan1213(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Support prepared statement invalidation when result types change
Date: 2024-01-07 08:16:48
Message-ID: CADT4RqD_vf8tV_O0kpMQhWr3UWMBt_BGgZhTkYPS3LSA5TwBCw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Sep 18, 2023 at 1:31 PM Jelte Fennema-Nio <me(at)jeltef(dot)nl> wrote:

> Furthermore caching RowDescription is also not super useful, most
> clients request it every time because it does not require an extra
> round trip, so there's almost no overhead in requesting it.

Just to point out, FWIW, that the .NET Npgsql driver does indeed cache
RowDescriptions... The whole point of preparation is to optimize things as
much as possible for repeated execution of the query; I get that the value
there is much lower than e.g. doing another network roundtrip, but that's
still extra work that's better off being cut if it can be.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrei Lepikhov 2024-01-07 10:22:59 Re: Multidimensional Histograms
Previous Message Andy Fan 2024-01-07 07:17:16 Re: Extract numeric filed in JSONB more effectively