Re: Adding nextval() to a select caused hang/very slow execution

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Eric Raskin <eraskin(at)paslists(dot)com>
Cc: pgsql-performance(at)lists(dot)postgresql(dot)org
Subject: Re: Adding nextval() to a select caused hang/very slow execution
Date: 2020-11-04 19:35:44
Message-ID: 1238445.1604518544@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

... btw, it occurs to me that at least as a stopgap,
"set enable_nestloop = off" would be worth trying.
The killer problem with rowcount-1 estimates is that they
encourage the planner to use nestloops when it shouldn't.

regards, tom lane

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message David Rowley 2020-11-04 20:13:22 Re: Partition pruning with joins
Previous Message Eric Raskin 2020-11-04 19:25:00 Re: Adding nextval() to a select caused hang/very slow execution