Tag Info

New answers tagged

3

All of this is unrelated to inheritance and partitioning. It's about indexing and query plans in general. The row size is much bigger for your second try: width=157 vs. width=46. Postgres will even more readily use an index for wider rows. Possible reasons for the unexpected sequential scan include: You have substantially fewer rows in your tables for the ...


1

From your query plans, it looks like you're comparing ints to ints in the first query plan, and int to numeric in the second plan. Your first compare: Index Cond: (("timestamp" >= 1431100800) AND ("timestamp" <= 1431108000)) and timestamp >= 1431100800 and timestamp <= 1431108000 In the second query, it's numeric values: Filter: ...



Top 50 recent answers are included