Re: POC: GROUP BY optimization

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrei Lepikhov <a(dot)lepikhov(at)postgrespro(dot)ru>
Cc: Alexander Korotkov <aekorotkov(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, Teodor Sigaev <teodor(at)sigaev(dot)ru>, David Rowley <dgrowleyml(at)gmail(dot)com>, "a(dot)rybakina" <a(dot)rybakina(at)postgrespro(dot)ru>, Белялов Дамир Наилевич <d(dot)belyalov(at)postgrespro(dot)ru>
Subject: Re: POC: GROUP BY optimization
Date: 2023-12-27 05:07:23
Message-ID: 2426725.1703653643@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrei Lepikhov <a(dot)lepikhov(at)postgrespro(dot)ru> writes:
> To be clear. In [1], I mentioned we can perform micro-benchmarks and
> structure costs of operators. At least for fixed-length operators, it is
> relatively easy.

I repeat what I said: this is a fool's errand. You will not get
trustworthy results even for the cases you measured, let alone
all the rest. I'd go as far as to say I would not believe your
microbenchmarks, because they would only apply for one platform,
compiler, backend build, phase of the moon, etc.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2023-12-27 06:06:13 Re: Synchronizing slots from primary to standby
Previous Message Rian McGuire 2023-12-27 04:44:09 [PATCH] pg_dump: Do not dump statistics for excluded tables