Re: [PATCH] avoid double scanning in function byteain

From: Aleksander Alekseev <aleksander(at)timescale(dot)com>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Cc: Stepan Neretin <slpmcf(at)gmail(dot)com>, Steven Niu <niushiji(at)gmail(dot)com>, Kirill Reshke <reshkekirill(at)gmail(dot)com>
Subject: Re: [PATCH] avoid double scanning in function byteain
Date: 2025-05-09 12:43:18
Message-ID: CAJ7c6TPvk-k6ZdC1YpkwWidtUntsEtCjocVkeKDJQ9Af28J_Eg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Stepan,

> Sorry for the noise — I'm resending the patch because I noticed a compiler warning related to mixed declarations and code, which I’ve now fixed.
>
> Apologies for the oversight in the previous submission.

Thanks for the patch.

As Kirill pointed out above, it would be nice if you could prove that
your implementation is actually faster. I think something like a
simple micro-benchmark will do.

--
Best regards,
Aleksander Alekseev

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Arseniy Mukhin 2025-05-09 12:43:46 Re: Amcheck verification of GiST and GIN
Previous Message Alena Rybakina 2025-05-09 12:31:11 Re: Vacuum statistics