Re: strange perf regression with data checksums

From: Mihail Nikalayeu <mihailnikalayeu(at)gmail(dot)com>
To: Peter Geoghegan <pg(at)bowt(dot)ie>
Cc: Tomas Vondra <tomas(at)vondra(dot)me>, Aleksander Alekseev <aleksander(at)timescale(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: strange perf regression with data checksums
Date: 2025-06-09 12:47:18
Message-ID: CADzfLwU9hs_icgckyiKga=LV3RYJyknwo7xN8xVn-sO3Dq+3hg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello, Peter!

>
> I also relocated the code that sets so.drop_pin from
> _bt_preprocess_keys to btrescan. That seems like the more logical
> place for it.
>

I was rebasing [0] and noticed dropPin is not initialized in
btbeginscan, which seems to be suspicious for me.
Is it intended?

[0]: https://commitfest.postgresql.org/patch/5151/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Xuneng Zhou 2025-06-09 13:25:19 Re: Add new wait event to XactLockTableWait
Previous Message jian he 2025-06-09 11:34:48 add column (query_start timestamptz) to progress report views