Search Postgresql Archives
Re: Search on very big (partitioned) table
[
Date Prev
][
Date Next
][
Thread Prev
][
Thread Next
][
Date Index
][
Thread Index
]
Subject
: Re: Search on very big (partitioned) table
From
: Adam Brusselback <adambrusselback@xxxxxxxxx>
Date
: Mon, 20 Feb 2017 15:47:36 -0500
In-reply-to
: <
88EF58F000EC4B4684700C2AA3A73D7A08054EACC730@W2008DC01.ColliniConsulting.lan
>
References
: <
88EF58F000EC4B4684700C2AA3A73D7A08054EACC730@W2008DC01.ColliniConsulting.lan
>
Do you have non overlapping check constraints on the partitions by date to allow the planner to exclude the child tables from needing to be looked at?
[
Date Prev
][
Date Next
][
Thread Prev
][
Thread Next
][
Date Index
][
Thread Index
]
Follow-Ups
:
Re: Search on very big (partitioned) table
From:
Sushant Pawar
References
:
Search on very big (partitioned) table
From:
Collini, ColliniConsulting.it
Prev by Date:
Re: Using xmin and xmax for optimistic locking
Next by Date:
Re: Using xmin and xmax for optimistic locking
Previous by thread:
Search on very big (partitioned) table
Next by thread:
Re: Search on very big (partitioned) table
Index(es):
Date
Thread
[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]
