Postgres Pro
Downloads
Home   >   mailing lists

Re: Optimize date query for large child tables: GiST or GIN? - Mailing list pgsql-performance

From David Jarvis
Subject Re: Optimize date query for large child tables: GiST or GIN?
Date
Msg-id AANLkTikOEC-Gr3eqGlyGauRAZJknQEaS5DEWw-ZOcl6r@mail.gmail.com
Whole thread Raw
In response to Re: Optimize date query for large child tables: GiST or GIN?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Optimize date query for large child tables: GiST or GIN?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-performance
Tree view
What if I were to have the application pass in two sets of date ranges?

For the condition of Dec 22 to Mar 22:

Dec 22 would become:
  • Dec 22 - Dec 31
Mar 22 would become:
  • Jan 1 - Mar 22
The first range would always be for the current year; the second range would always be for the year following the current year.

Would that allow PostgreSQL to use the index?

Dave

pgsql-performance by date:

Previous
From: Tom Lane
Date:
Subject: Re: Optimize date query for large child tables: GiST or GIN?
Next
From: Tom Lane
Date:
Subject: Re: Optimize date query for large child tables: GiST or GIN?