Re: Unworkable plan above certain row count

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: André Hänsel <andre(at)webkr(dot)de>
Cc: pgsql-performance(at)lists(dot)postgresql(dot)org
Subject: Re: Unworkable plan above certain row count
Date: 2022-04-28 02:08:14
Message-ID: 503301.1651111694@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

=?iso-8859-1?Q?Andr=E9_H=E4nsel?= <andre(at)webkr(dot)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

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Emil Iggland 2022-04-28 08:09:55 Re: Performance differential when 0 values present vs when 1 values present. Planner return 52k rows when 0 expected.
Previous Message André Hänsel 2022-04-28 00:52:57 Unworkable plan above certain row count