Search Postgresql Archives

Indexes that would span partitions.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



What's a good strategy for dealing with indexes (multiple) that would
span multiple partitions of a table.

For example:

Let's  say I have a table that's partitioned by group_id because I
want all the records for a group to be in the same partition. Let's
say I have a field called "expires_at" which is a date. Let's presume
the expiry date can be updated.

If I want to do something to every record that is due to be expired
the database is going to be touching practically every partition and
this seems like it could present a problem.

Is there a more efficient way to deal with something like this?





[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]

  Powered by Linux