Search Postgresql Archives

Re: general question on two-partition table

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

 



On Tue, Jul 28, 2009 at 1:08 AM, David Wilson<david.t.wilson@xxxxxxxxx> wrote:
> On Mon, Jul 27, 2009 at 7:52 PM, Janet Jacobsen<jsjacobsen@xxxxxxx> wrote:
>
>> Can you suggest other strategies?
>
> Something that might be easier to play with is to create a (or
> several, to speed up other queries) functional index on the comparison
> between rbscore and the cutoff.

I think it would be even more interesting to have partial indexes --
ie specified with "WHERE rbscore < cutoff".

I'm actually wondering if partitioning is really what you want. You
might prefer to just keep two entirely separate tables. One that has
all the data and one that has a second copy of the desirable subset.
Kind of like a "materialized view" of a simple query with the where
clause of "rbscore < cutoff".


-- 
greg
http://mit.edu/~gsstark/resume.pdf

-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

[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 Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux