Re: PostgreSQL opens all the indexes of a relation for every Query during Planning Time?

From: Jason Petersen <jason(at)citusdata(dot)com>
To: Meenatchi Sandanam <meen(dot)opm(at)gmail(dot)com>
Cc: pgsql-performance-owner(at)lists(dot)postgresql(dot)org, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: PostgreSQL opens all the indexes of a relation for every Query during Planning Time?
Date: 2018-03-16 17:18:41
Message-ID: 430DECAC-2702-4B12-A19B-1E1C3BCE27BE@citusdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On Mar 15, 2018, at 4:18 AM, Meenatchi Sandanam <meen(dot)opm(at)gmail(dot)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
jason(at)citusdata(dot)com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2018-03-16 17:29:58 Re: chained transactions
Previous Message Ashutosh Bapat 2018-03-16 17:18:35 Re: [HACKERS] Partition-wise aggregation/grouping