This particular use case is for user behavior data mining. The hardware is beefy, and has tablespaces split out onto SSD/spindle for new & old data. All of my queries are pretty much a nightly cron process, and I don't really care too much about the speed. Scanning the full 4 years of data takes about 30 seconds per query anyway... but I thought it'd be nice to speed it up when the difference is milliseconds vs 30 seconds.
On Fri, Sep 5, 2014 at 4:17 PM, John R Pierce <pierce@xxxxxxxxxxxx> wrote:
On 9/5/2014 10:31 AM, Cal Heldenbrand wrote:
Number of child tables: 1581
that's an insane number of children. We try and limit it to 50 or so child tables, for instance, 6 months retention by week, of data will millions of rows/day.
-- john r pierce 37N 122W somewhere on the middle of the left coast
