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 indexes on the same
> >>> column?
>
> >> There is non
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.
>> different opclasses and/or index AMs).
> We
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 index AMs).
Well, it can be beneficia
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/indexes.html
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?
