message, or any action or omission
taken by you in reliance on it is prohibited.
Please contact the sender immediately if you have received this message by
mistake.
Thank you for your cooperation.
De: David Rowley
Enviado: 18 de dezembro de 2022 11:06
Para: Jo
On Sun, 18 Dec 2022 at 23:44, João Paulo Luís wrote:
> Meanwhile, as a one-time workaround I've disabled the hashagg algorithm,
The way the query planner determines if Hash Aggregate's hash table
will fit in work_mem or not is based on the n_distinct estimate of the
columns being grouped on.
he sender immediately if you have received this message by
mistake.
Thank you for your cooperation.
De: Justin Pryzby
Enviado: 16 de dezembro de 2022 16:06
Para: João Paulo Luís
Cc: pgsql-performance@lists.postgresql.org
Assunto: Re: Postgres12 looking for possible Hash
On Fri, Dec 16, 2022 at 03:24:17PM +, João Paulo Luís wrote:
> Hi! Sorry to post to this mailing list, but I could not find many tips
> working around HashAggregate issues.
>
> In a research project involving text repetition analysis (on top of public
> documents)
> I have a VirtualMachine
Hi! Sorry to post to this mailing list, but I could not find many tips working
around HashAggregate issues.
In a research project involving text repetition analysis (on top of public
documents)
I have a VirtualMachine (CPU AMD Epyc 7502P, 128GB RAM, 12TB HDD, 2TB SSD),
running postgres 12.12
