> On Mar 15, 2018, at 4:18 AM, Meenatchi Sandanam <meen....@gmail.com> wrote: > > On checking PostgreSQL code, we see it opens all indexes of a relation for > every query planning time as in the attachment. If that is the case, it might > lead to Performance degradation for relations with many indexes. Is there any > other better way to handle this like Scanning/Opening only the indexes > related to columns specified in the query?
I’d think you’d need a pretty clear profiling run that points to this as a hot spot before deciding to optimize it. Do you have a query where this is the case? -- Jason Petersen Software Engineer | Citus Data 303.736.9255 ja...@citusdata.com
