| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | David Fetter <david(at)fetter(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Cc: | John Naylor <john(dot)naylor(at)enterprisedb(dot)com> |
| Subject: | Re: popcount |
| Date: | 2021-03-20 20:01:25 |
| Message-ID: | 775b91fc-80fa-179d-bb20-0bf230e6db40@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 18.03.21 13:51, John Naylor wrote:
> Hi David,
>
> Just a nitpick:
>
> +SET bytea_output TO hex;
>
> Since we don't see the string in the output, I don't immediately see the
> reason to change the output format here?
>
> Aside from that, this patch works as expected, and is ready for committer.
I have now read the entire internet on what a suitable name for this
function could be. I think the emerging winner is BIT_COUNT(), which
already exists in MySQL, and also in Python (int.bit_count()) and Java
(Integer.bitCount()).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2021-03-20 20:37:51 | Re: [HACKERS] Custom compression methods |
| Previous Message | Tom Lane | 2021-03-20 19:03:50 | Re: [HACKERS] Custom compression methods |