for declarative partition- ing. Considerable care is needed in deciding whether partitioning with legacy inheritance is useful for your application. 5.11. Table Partitioning PostgreSQL supports basic table technique similar to partition pruning. While it is primarily used for partitioning implemented using the legacy inheritance method, it can be used for other purposes, including with declarative partitioning. exclusion, so large numbers of children are likely to increase query planning time considerably. So the legacy inheritance based partitioning will work well with up to perhaps a hundred child tables; don't try

for declarative parti- tioning. Considerable care is needed in deciding whether partitioning with legacy inheritance is useful for your application. 5.11. Table Partitioning PostgreSQL supports basic table similar to partition pruning. While it is primar- ily used for partitioning implemented using the legacy inheritance method, it can be used for other purposes, including with declarative partitioning. exclusion, so large numbers of children are likely to increase query planning time considerably. So the legacy inheri- tance based partitioning will work well with up to perhaps a hundred child tables; don't

for declarative partition- ing. Considerable care is needed in deciding whether partitioning with legacy inheritance is useful for your application. 5.11. Table Partitioning PostgreSQL supports basic technique similar to partition pruning. While it is primarily used for partitioning implemented using the legacy inheritance method, it can be used for other purposes, including with declarative partitioning. exclusion, so large numbers of children are likely to increase query planning time considerably. So the legacy inheritance based partitioning will work well with up to perhaps a hundred child tables; don't try

for declarative parti- tioning. Considerable care is needed in deciding whether partitioning with legacy inheritance is useful for your application. 5.11. Table Partitioning PostgreSQL supports basic similar to partition pruning. While it is primar- ily used for partitioning implemented using the legacy inheritance method, it can be used for other purposes, including with declarative partitioning. exclusion, so large numbers of children are likely to increase query planning time considerably. So the legacy inheri- tance based partitioning will work well with up to perhaps a hundred child tables; don't

for declarative parti- tioning. Considerable care is needed in deciding whether partitioning with legacy inheritance is useful for your application. 5.11. Table Partitioning PostgreSQL supports basic similar to partition pruning. While it is primar- ily used for partitioning implemented using the legacy inheritance method, it can be used for other purposes, including with declarative partitioning. exclusion, so large numbers of children are likely to increase query planning time considerably. So the legacy inheri- tance based partitioning will work well with up to perhaps a hundred child tables; don't

for declarative partition- ing. Considerable care is needed in deciding whether partitioning with legacy inheritance is useful for your application. 5.11. Table Partitioning PostgreSQL supports basic technique similar to partition pruning. While it is primarily used for partitioning implemented using the legacy inheritance method, it can be used for other purposes, including with declarative partitioning. exclusion, so large numbers of children are likely to increase query planning time considerably. So the legacy inheritance based partitioning will work well with up to perhaps a hundred child tables; don't try

for declarative parti- tioning. Considerable care is needed in deciding whether partitioning with legacy inheritance is useful for your application. 5.10. Table Partitioning PostgreSQL supports basic table similar to partition pruning. While it is primar- ily used for partitioning implemented using the legacy inheritance method, it can be used for other purposes, including with declarative partitioning. exclusion, so large numbers of children are likely to increase query planning time considerably. So the legacy inheri- tance based partitioning will work well with up to perhaps a hundred child tables; don't

for declarative parti- tioning. Considerable care is needed in deciding whether partitioning with legacy inheritance is useful for your application. 5.11. Table Partitioning PostgreSQL supports basic table similar to partition pruning. While it is primar- ily used for partitioning implemented using the legacy inheritance method, it can be used for other purposes, including with declarative partitioning. exclusion, so large numbers of children are likely to increase query planning time considerably. So the legacy inheri- tance based partitioning will work well with up to perhaps a hundred child tables; don't

for declarative parti- tioning. Considerable care is needed in deciding whether partitioning with legacy inheritance is useful for your application. 5.11. Table Partitioning PostgreSQL supports basic similar to partition pruning. While it is primar- ily used for partitioning implemented using the legacy inheritance method, it can be used for other purposes, including with declarative partitioning. exclusion, so large numbers of children are likely to increase query planning time considerably. So the legacy inheri- tance based partitioning will work well with up to perhaps a hundred child tables; don't

for declarative partition- ing. Considerable care is needed in deciding whether partitioning with legacy inheritance is useful for your application. 5.10. Table Partitioning PostgreSQL supports basic technique similar to partition pruning. While it is primarily used for partitioning implemented using the legacy inheritance method, it can be used for other purposes, including with declarative partitioning. exclusion, so large numbers of children are likely to increase query planning time considerably. So the legacy inheritance based partitioning will work well with up to perhaps a hundred child tables; don't try