Re: Buffer usage detailed by RelKind in EXPLAIN ANALYZE BUFFERS

From: Andres Freund <andres(at)anarazel(dot)de>
To: Andrey Borodin <amborodin86(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Buffer usage detailed by RelKind in EXPLAIN ANALYZE BUFFERS
Date: 2023-02-14 00:29:57
Message-ID: 20230214002957.bfdg2we3ch6v7mqo@awork3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 2023-02-13 16:23:30 -0800, Andrey Borodin wrote:
> But there are some caveats:
> 1. Some more increments on hot paths. We have to add this tiny toll to
> every single buffer hit, but it will be seldom of any use.

Additionally, I bet it slows down EXPLAIN (ANALYZE, BUFFERS) noticeably. It's
already quite expensive...

> All in all I do not have an opinion if this feature is a good tradeoff.
> What do you think? Does the feature look useful? Do we want a more
> polished implementation?

Unless the above issues could be avoided, I don't think so.

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2023-02-14 00:33:06 Re: Make EXPLAIN generate a generic plan for a parameterized query
Previous Message Andres Freund 2023-02-14 00:26:27 Re: Add the ability to limit the amount of memory that can be allocated to backends.