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 (Ub
"Render Comunicacion S.L." writes:
> The issue:
> When we search our locator with section_id: 1 (or any number < 4), PostgreSQL
> takes around 4, 5000, 8000ms or more.
> When we search our locator with section_id: 4 (or any other bigger number),
> PostgreSQL takes around 100 ms. ( ~ expected
Hello to everyone
I'm new here, and I hope that my question is on the correct mail-list.
We use PostgreSQL to store JSON-B in different tables, all tables have the same
schema and all tables are indexed with GIN index for the JSON data.
We use two properties of the JSON to locate data:
{
