按“字段”和限制的慢顺序

时间:2018-09-25 16:32:29

标签: postgresql

我有一个简单的查询,该查询必须从具有约1400万条记录的表中获取1条记录:

EXPLAIN ANALYZE SELECT "projects_toolresult"."id", 
"projects_toolresult"."tool_id", 
"projects_toolresult"."status",
"projects_toolresult"."updated_at",
"projects_toolresult"."created_at" FROM 
"projects_toolresult" WHERE 
("projects_toolresult"."status" = 1 AND 
"projects_toolresult"."tool_id" = 21)
 ORDER BY "projects_toolresult"."updated_at"
 DESC LIMIT 1;

奇怪的是,当我通过updated_at字段订购查询时,我的查询执行了60秒。

Limit  (cost=0.43..510.94 rows=1 width=151) (actual
time=56754.932..56754.932 rows=0 loops=1)
->  Index Scan using projects_to_updated_266459_idx on projects_toolresult  (cost=0.43..1800549.09 rows=3527 width=151) (actual time=56754.930..56754.930 rows=0 loops=1)
         Filter: ((status = 1) AND (tool_id = 21))
         Rows Removed by Filter: 13709343  Planning time: 0.236 ms  Execution time: 56754.968 ms (6 rows)

无论是ASC还是DESC

但是如果我做ORDER BY RAND()或没有命令:

Limit  (cost=23496.10..23496.10 rows=1 width=151) (actual time=447.532..447.532 rows=0 loops=1)
   ->  Sort  (cost=23496.10..23505.20 rows=3642 width=151) (actual time=447.530..447.530 rows=0 loops=1)
         Sort Key: (random())
         Sort Method: quicksort  Memory: 25kB
         ->  Index Scan using projects_toolresult_tool_id_34a3bb16 on projects_toolresult  (cost=0.56..23477.89 rows=3642 width=151) (actual time=447.513..447.513 rows=0 loops=1)
               Index Cond: (tool_id = 21)
               Filter: (status = 1)
               Rows Removed by Filter: 6097
 Planning time: 0.224 ms
 Execution time: 447.571 ms
(10 rows)

工作迅速。

我在updated_atstatus字段上有索引(我也尝试过没有索引)。我确实升级了默认的postgres设置,并使用此生成器增加了值:https://pgtune.leopard.in.ua/#/

enter image description here

这就是在执行查询时发生的情况。

Postgres版本 9.5

我的表和索引:

id              | integer                  | not null default nextval('projects_toolresult_id_seq'::regclass)
 status          | smallint                 | not null
 object_id       | integer                  | not null
 created_at      | timestamp with time zone | not null
 content_type_id | integer                  | not null
 tool_id         | integer                  | not null
 updated_at      | timestamp with time zone | not null
 output_data     | text                     | not null
Indexes:
    "projects_toolresult_pkey" PRIMARY KEY, btree (id)
    "projects_toolresult_content_type_id_object_i_71ee2c2e_uniq" UNIQUE CONSTRAINT, btree (content_type_id, object_id, tool_id)
    "projects_to_created_cee389_idx" btree (created_at)
    "projects_to_tool_id_ec7856_idx" btree (tool_id, status)
    "projects_to_updated_266459_idx" btree (updated_at)
    "projects_toolresult_content_type_id_9924d905" btree (content_type_id)
    "projects_toolresult_tool_id_34a3bb16" btree (tool_id)
Check constraints:
    "projects_toolresult_object_id_check" CHECK (object_id >= 0)
    "projects_toolresult_status_check" CHECK (status >= 0)
Foreign-key constraints:
    "projects_toolresult_content_type_id_9924d905_fk_django_co" FOREIGN KEY (content_type_id) REFERENCES django_content_type(id) DEFERRABLE INITIALLY DEFERRED
    "projects_toolresult_tool_id_34a3bb16_fk_projects_tool_id" FOREIGN KEY (tool_id) REFERENCES projects_tool(id) DEFERRABLE INITIALLY DEFERRED

1 个答案:

答案 0 :(得分:2)

您正在statustool_id上过滤数据,并在updated_at上进行排序,但是所有这三列都没有单个索引。

添加索引,如下所示:

CREATE INDEX ON projects_toolresult (status, tool_id, updated_at);