From: | Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com> |
---|---|
To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Partition : Append node over a single SeqScan |
Date: | 2017-07-05 10:18:39 |
Message-ID: | CAE9k0PnySTqN_6fLYHHM5cU2J3sxZwEZjFWYJrH0R1=SiPzA8A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi All,
Today while exploring a bit on Range table partitioning, I could see
that even if scan is performed on a single partition, the plan node
has Append node in it. Isn't it a bug?
As per the usage of Append Node, it should only be seen in the
queryplan when scan is performed on multiple tables.
Following are the steps to reproduce the problem.
CREATE TABLE part_tab (c1 int, c2 int) PARTITION BY RANGE (c1);
CREATE TABLE part1 PARTITION OF part_tab FOR VALUES FROM (0) TO (100);
CREATE TABLE part2 PARTITION OF part_tab FOR VALUES FROM (100) TO (200);
postgres=# explain analyze select * from part_tab where c1 > 100;
QUERY PLAN
--------------------------------------------------------------------------------------------------------
Append (cost=0.00..38.25 rows=753 width=8) (actual time=0.009..0.009
rows=0 loops=1)
-> Seq Scan on part2 (cost=0.00..38.25 rows=753 width=8) (actual
time=0.009..0.009 rows=0 loops=1)
Filter: (c1 > 100)
Planning time: 166698.973 ms
Execution time: 0.043 ms
(5 rows)
--
With Regards,
Ashutosh Sharma
EnterpriseDB:http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Ashutosh Bapat | 2017-07-05 10:28:59 | Re: Partition : Append node over a single SeqScan |
Previous Message | Amit Langote | 2017-07-05 09:43:13 | Re: Multi column range partition table |