Re: Optimize date query for large child tables: GiST or GIN?
От
David Jarvis
Тема
Re: Optimize date query for large child tables: GiST or
GIN?
Дата
Msg-id
AANLkTik288XsL9ie_N7QwGHjYiQ3xGY4iTNtucfsCe3v@mail.gmail.com
Ответ на
Re: Optimize date query for large child tables: GiST or GIN? (Alvaro Herrera)
Список
Дерево обсуждения
Optimize date query for large child tables: GiST or GIN? David Jarvis <thangalin@gmail.com>
Re: Optimize date query for large child tables: GiST or
GIN? Stephen Frost <sfrost@snowman.net>
Re: Optimize date query for large child tables: GiST or
GIN? David Jarvis <thangalin@gmail.com>
Re: Optimize date query for large child tables: GiST or
GIN? Yeb Havinga <yebhavinga@gmail.com>
Re: Optimize date query for large child tables: GiST or
GIN? Thom Brown <thombrown@gmail.com>
Re: Optimize date query for large child tables: GiST or
GIN? Matthew Wakeling <matthew@flymine.org>
Re: Optimize date query for large child tables: GiST or GIN? Tom Lane <tgl@sss.pgh.pa.us>
Re: Optimize date query for large child tables: GiST or
GIN? David Jarvis <thangalin@gmail.com>
Hi,
Not an issue; the inserts are one-time (or very rare; at most: once a year).
The seven child tables (split on category ID) have the following indexes:
Dave
Hmm, that's nice, though I cannot but wonder whether the exclusive lock
required by CLUSTER is going to be a problem in the long run.
Not an issue; the inserts are one-time (or very rare; at most: once a year).
Hm, keep in mind that if the station clause alone is not selective
enough, scanning it may be too expensive. The current three column
The seven child tables (split on category ID) have the following indexes:
- Primary key (unique ID, sequence)
- Station ID (table data is physically inserted by station ID order)
- Station ID, Date, and Category ID (this index is CLUSTER'ed)
Dave
В списке pgsql-performance по дате отправления
От: David Jarvis
Дата:
