Timeline for Index not being used in PostgreSQL
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 14, 2015 at 15:56 | comment | added | laurt | This did not help, query still uses seq scan. | |
| Dec 14, 2015 at 13:57 | comment | added | ypercubeᵀᴹ |
You can also try WITH t2 AS (SELECT id FROM table2 WHERE table3_fk = 3) SELECT * FROM table1 WHERE table2_fk IN (TABLE t2) ;
|
|
| Dec 14, 2015 at 13:44 | comment | added | Pivobispo | It will tell Postges to evaluate the subquery first. I had the problem as you some time ago and adding that solved my problem. | |
| Dec 14, 2015 at 13:43 | comment | added | András Váczi | Ah. But what difference will it make? | |
| Dec 14, 2015 at 13:41 | comment | added | Pivobispo | The right word is OFFSET, sorry. | |
| Dec 14, 2015 at 13:40 | history | edited | Pivobispo | CC BY-SA 3.0 |
deleted 1 character in body
|
| Dec 14, 2015 at 13:35 | comment | added | András Váczi | Are you sure this is valid in PostgreSQL? | |
| Dec 14, 2015 at 13:13 | history | answered | Pivobispo | CC BY-SA 3.0 |