Justin Pryzby <pryzby@xxxxxxxxxxxxx> writes: > I believe the join is being (badly) underestimated, leading to a crappy plan > involving multiple nested loop joins, which takes 2.5 hours instead of a > handful of seconds; I believe that might be resolved by populating its MCV > list.. With only two rows in the table, I'm not real sure why you'd need an MCV list. Could we see the actual problem query (and the other table schemas), rather than diving into the code first? regards, tom lane -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
