Got it! Thanks Andres and Tom!
Tiff
On Fri, Apr 12, 2019 at 1:07 PM Tom Lane wrote:
> Andres Freund writes:
> > On 2019-04-12 09:51:51 -0400, Tom Lane wrote:
> >> Tiffany Thang writes:
> >>> Can someone explain the use of creating multiple in
Andres Freund writes:
> On 2019-04-12 09:51:51 -0400, Tom Lane wrote:
>> Tiffany Thang writes:
>>> Can someone explain the use of creating multiple indexes on the same
>>> column?
>> There is none, unless the indexes have different properties (e.g.
>&g
Hi,
On 2019-04-12 09:51:51 -0400, Tom Lane wrote:
> Tiffany Thang writes:
> > Can someone explain the use of creating multiple indexes on the same
> > column?
>
> There is none, unless the indexes have different properties (e.g.
> different opclasses and/or i
Tiffany Thang writes:
> Can someone explain the use of creating multiple indexes on the same
> column?
There is none, unless the indexes have different properties (e.g.
different opclasses and/or index AMs).
I'd suggest reading
https://www.postgresql.org/docs/current/indexe
On Fri, 12 Apr 2019 at 11:54, Tiffany Thang wrote:
> Can you provide a scenario where creating multiple indexes on the same
> column would be beneficial?
>
When you have too much disk space?
When your table writes are too fast?
Hi,
Can someone explain the use of creating multiple indexes on the same
column?
How would the optimizer determine which index to use? From my brief
testing, the optimizer picked the latest created index, testidx3. Can you
provide a scenario where creating multiple indexes on the same column
