Re: [PERFORM] 100% CPU Utilization when we run queries.

Hi, Sorry. I am posting the query details below. Query: SELECT DISTINCT events_rpt_v3.init_service_comp FROM public.events_rpt_v3 events_rpt_v3; events_rpt_v3 is a view based on partition tables. Number of rows in events_rpt_v3: 57878 vmstat o/p: procs ---memory-- ---swap--

Re: [PERFORM] need to repeat the same condition on joined tables in order to choose the proper plan

Thanks Tom, this explain the behavior. But is there a more elegant way to achieve the only acceptable plan (index scan on both tables) without that ugly syntax? It does seem to me like a specific syntax to help the current postgressql planner make the right decision. ( I am aware about the radical