On Wednesday 01 October 2008 03:34, Gauri Kanekar wrote:
> -> Nested Loop (cost=186.26..647160.32 rows=42543 width=16) (actual
> time=655.832..6622.011 rows=5120582 loops=1)
That nested loop estimate is off by 100x, which is why the DB is using a
slow nested loop for a large amount of data.
On Wed, 1 Oct 2008, Gauri Kanekar wrote:
"new_table1" is 18% of the the whole "table1".
-> Nested Loop (cost=186.26..647160.32 rows=42543 width=16) (actual
time=655.832..6622.011 rows=5120582 loops=1)
-> Nested Loop (cost=0.00..414246.81 rows=25155 width=16) (actual
time=19.578.
Hi,
We have a table called "table1" which contains around 638725448 records.
We created a subset of this table and named it as "new_table1" which has
around 120107519 records.
"new_table1" is 18% of the the whole "table1".
If we fire the below queries we are not finding any drastic performance
g
