Re: Unworkable plan above certain row count - Mailing list pgsql-performance

From Tom Lane
Subject Re: Unworkable plan above certain row count
Date
Msg-id 503301.1651111694@sss.pgh.pa.us
Whole thread Raw
In response to Unworkable plan above certain row count  (André Hänsel <andre@webkr.de>)
List pgsql-performance
=?iso-8859-1?Q?Andr=E9_H=E4nsel?= <andre@webkr.de> writes:
> Now if you change
> INSERT INTO a(a_id) SELECT generate_series(1, 20000);
> to
> INSERT INTO a(a_id) SELECT generate_series(1, 200000);
> i.e. add a zero, the plan becomes [ not a hashed subplan ]

Yeah, it won't hash the subplan if the estimated size of the hash
table exceeds work_mem.  In this case, boosting work_mem would be
a mighty good idea.

            regards, tom lane



pgsql-performance by date:

Previous
From: André Hänsel
Date:
Subject: Unworkable plan above certain row count
Next
From: Emil Iggland
Date:
Subject: Re: Performance differential when 0 values present vs when 1 values present. Planner return 52k rows when 0 expected.