Hello, I'm finding that the "NULLS LAST" query takes 65 seconds to return 372 rows, while the "AND RECHECK.capture_time IS NOT null" takes 1.3 seconds to return 372 rows.
We are running PG 9.4 yet, so that version is probably missing an optimization that makes the nulls first faster.
The explain analyze seems to be saying that the call number join is what is blowing it up, evaluating 250 million rows for some reason.
We will use the "AND RECHECK.capture_time IS NOT null" until we upgrade to a newer PG version.
Josh
Hello, I'm finding that the "NULLS LAST" query takes 65 seconds to return 372 rows, while the "AND RECHECK. capture_ time IS NOT null" takes 1.3 seconds to return 372 rows.
We are running PG 9.4 yet, so that version is probably missing an optimization that makes the nulls first faster.
The explain analyze seems to be saying that the call number join is what is blowing it up, evaluating 250 million rows for some reason.
We will use the "AND RECHECK. capture_ time IS NOT null" until we upgrade to a newer PG version.
Josh