Table Partitioning and Indexes Performance Questions - Mailing list pgsql-performance

From David Kelly
Subject Table Partitioning and Indexes Performance Questions
Date
Msg-id CAOB7Wd2+T0D9qthyVkz61wv370xyoR9toPv7y3=LJRsjD7yx3Q@mail.gmail.com
Whole thread Raw
Responses Re: Table Partitioning and Indexes Performance Questions  (Laurenz Albe <laurenz.albe@cybertec.at>)
List pgsql-performance
I was told that partitioned table indexed must always start with the partition key columns. 

Is this always the case or does it depend on use case? When would you want to create indexes in this way?

The documentation just mentions that it is strictly unnecessary but can be helpful. My understanding is partitions behave like normal tables. Each gets their own index. So, I'd expect the reasoning behind creating the index on the partition should be the same as if it were just a normal table (assuming it has the same subset of data as the individual partition). Is this a correct understanding? 

Any other performance considerations when it comes to partitioned table indexing? Specifically, partitioning by range where the range is a single value.

pgsql-performance by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: generic plan generate poor performance
Next
From: Laurenz Albe
Date:
Subject: Re: Table Partitioning and Indexes Performance Questions