1

我无法相信我通过带有 ORDER BY 子句的简单选择所看到的。这是我的查询和错误结果：

SELECT date_valid, id_variable FROM myTable
   WHERE id_stn='78224' AND date_valid BETWEEN '2014-07-03 09:00:00'
         AND '2014-07-03 21:00:00' AND id_variable IN (11012,12004)
   ORDER BY date_valid ;

     date_valid      | id_variable 
---------------------+-------------
 2014-07-03 09:00:00 |       11012
 2014-07-03 15:00:00 |       11012
 2014-07-03 21:00:00 |       11012
 2014-07-03 09:00:00 |       12004
 2014-07-03 15:00:00 |       12004
 2014-07-03 21:00:00 |       12004

如您所见，排序似乎是在id_variable而不是date_valid上完成的。为了获得预期的结果，我必须创建一个 Postgresql 无法优化的新字段或提供超过 1 天的时间戳范围：

SELECT date_valid,id_variable FROM myTable
       WHERE id_stn='78224' AND date_valid BETWEEN '2014-07-03 09:00:00'
             AND '2014-07-03 21:00:00' AND id_variable IN (11012,12004)
       ORDER BY date_valid + '0 hours'::INTERVAL;

     date_valid      | id_variable
---------------------+-------------
 2014-07-03 09:00:00 |       11012
 2014-07-03 09:00:00 |       12004
 2014-07-03 15:00:00 |       11012
 2014-07-03 15:00:00 |       12004
 2014-07-03 21:00:00 |       11012
 2014-07-03 21:00:00 |       12004

这是一个部分表定义，它在每个月的 date_valid 上进行分区：

    Column     |            Type
---------------+-----------------------------
 id_obs        | bigint                      
 date_valid    | timestamp without time zone
 id_variable   | integer
 id_stn        | character varying(50)
Indexes:
    "myTable_pkey" PRIMARY KEY, btree (id_obs)
    "myTable_ukey" UNIQUE CONSTRAINT, btree (date_valid, id_variable, lat, lon)
Check constraints:
    "myTable_date_valid_check" CHECK (date_valid >= '2014-07-01 00:00:00'::timestamp without time zone AND date_valid < '2014-08-01 00:00:00'::timestamp without time zone)
Triggers:
    myTable_before_update BEFORE UPDATE ON myTable_201407 FOR EACH ROW EXECUTE PROCEDURE obs_update()
Inherits: myTable_parent
Has OIDs: no

如果结果在同一天，Postgresql 不会按小时排序似乎是一个错误。这一定是一个优化器问题，因为如果我对另一个未编入索引的时间戳字段进行排序，我就没有这个问题。如果我在每个日期字符串之后指定 ::TIMESTAMP，或者如果我将选择包含在另一个上，则结果是相同的（未排序）：SELECT * FROM (SELECT ...) x ORDER BY DATE_VALID。我对其他具有类似结构的表也有同样的问题。

这是 Postgresql 9.2.8 的解释结果：

 Result  (cost=0.02..62864.86 rows=10 width=87)
   ->  Merge Append  (cost=0.02..62864.86 rows=10 width=87)
         Sort Key: myTable.date_valid
         ->  Sort  (cost=0.01..0.02 rows=1 width=220)
               Sort Key: myTable.date_valid
               ->  Seq Scan on myTable  (cost=0.00..0.00 rows=1 width=220)
                     Filter: ((date_valid >= '2014-07-03 09:00:00'::timestamp without time zone) AND (date_valid <= '2014-07-03 21:00:00'::timestamp without time zone) AND (id_variable = ANY ('{11012,12004}'::integer[])) AND ((id
_stn)::text = '78224'::text))
         ->  Index Scan using myTable_201407_ukey on myTable_201407 myTable  (cost=0.00..62864.71 rows=9 width=72)
               Index Cond: ((date_valid >= '2014-07-03 09:00:00'::timestamp without time zone) AND (date_valid <= '2014-07-03 21:00:00'::timestamp without time zone) AND (id_variable = ANY ('{11012,12004}'::integer[])))
               Filter: ((id_stn)::text = '78224'::text)
4

1 回答 1

1

可能在 9.2.1 中修复了这个错误

修复涉及 WHERE indexed_column IN (list_of_values) 的查询的输出排序可能不正确

http://www.postgresql.org/docs/9.2/static/release-9-2-1.html

9.2 已经是 9.2.8

于 2014-07-11T09:45:25.990 回答