| From: | Andrei Lepikhov <lepihov(at)gmail(dot)com> |
|---|---|
| To: | Alena Rybakina <lena(dot)ribackina(at)yandex(dot)ru>, pgsql-hackers(at)postgresql(dot)org |
| Cc: | Nikolay Samokhvalov <samokhvalov(at)gmail(dot)com>, Ilia Evdokimov <ilya(dot)evdokimov(at)tantorlabs(dot)com> |
| Subject: | Re: Add rows removed by hash join clause to instrumentation |
| Date: | 2026-01-19 19:44:56 |
| Message-ID: | fb60811a-9053-4520-a2a1-209344367fd5@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 19/1/26 20:33, Alena Rybakina wrote:
> I’ve looked through the patch and didn’t spot any obvious issues.
> Instrumentation of this kind is not something we usually test in
> regression tests, but I’ve added a small patch with some test coverage
> and attached it here. For now, I don't have any more suggestions.
I doubt if the 'Rows Removed by Hash Matching' has a platform-stable
value. It makes 'Removed By Join Filter' unstable, too. So, not sure if
specific values may be used in regression tests. Am I wrong?
--
regards, Andrei Lepikhov,
pgEdge
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matthias van de Meent | 2026-01-19 19:45:40 | Re: index prefetching |
| Previous Message | Alena Rybakina | 2026-01-19 19:33:06 | Re: Add rows removed by hash join clause to instrumentation |