Re: One Partition by list is always chosen by planner

2017-11-22 Thread legrand legrand
Hello, thank you for this answer. I just wanted to add a few informations. This table has in fact around 20 partitions, explain select * from wiki_data_part where category='fr' returns only 2 partitions (meaning that constraint_exclusion works) the partition that is always scanned has more tha

Re: One Partition by list is always chosen by planner

2017-11-21 Thread Kyotaro HORIGUCHI
Hello, It seems to me that the type of category is not text and the right side in the query is actually casted to text. At Tue, 21 Nov 2017 12:23:02 -0700 (MST), legrand legrand wrote in <1511292182893-0.p...@n3.nabble.com> > and if I explain the same query with an other filter > > explain sel

Re: One Partition by list is always chosen by planner

2017-11-21 Thread legrand legrand
yes it is show constraint_exclusion partition and if I explain the same query with an other filter explain select * from wiki_data_part where category='fr' | Append (cost=0.00..14010.76 rows=291609 width=48)

Re: One Partition by list is always chosen by planner

2017-11-21 Thread Hellmuth Vargas
Hi what is the value of the parameter "constraint_exclusion" (in postgresq.conf)? You must set: constraint_exclusion = partition 2017-11-20 17:54 GMT-05:00 legrand legrand : > Hello, > > after creating a table wiki_data_part with > partition by list (category); > > and creating partitions lik

One Partition by list is always chosen by planner

2017-11-20 Thread legrand legrand
Hello, after creating a table wiki_data_part with partition by list (category); and creating partitions like CREATE TABLE wiki_data_part_a PARTITION OF wiki_data_part FOR VALUES IN ('ang.q',...,'arc'); CREATE TABLE wiki_data_part_b PARTITION OF wiki_data_part FOR VALUES IN ('bs.s',...,'bg.n'); c