| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Mihail Nikalayeu <mihailnikalayeu(at)gmail(dot)com> |
| 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 14:49:27 |
| Message-ID: | CAH2-WzmX2DFus=XY5hvGPFq11gHLXL==qTQDaXbX=S7tKk0rvQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jun 9, 2025 at 8:48 AM Mihail Nikalayeu
<mihailnikalayeu(at)gmail(dot)com> wrote:
> I was rebasing [0] and noticed dropPin is not initialized in
> btbeginscan, which seems to be suspicious for me.
> Is it intended?
That's pretty normal. We don't have access to the scan descriptor
within btbeginscan.
This is also why we do things like allocate so->currTuples within
btrescan. We don't yet know if the scan will be an index-only scan
when btbeginscan is called.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sami Imseih | 2025-06-09 15:09:00 | Re: queryId constant squashing does not support prepared statements |
| Previous Message | Peter Geoghegan | 2025-06-09 14:47:35 | Re: strange perf regression with data checksums |