Re: 2D partitioning of VLDB - sane or not?

Jason,

> Which brings us back to the original issue. If I decide to stick with
> the current implementation and not "improve our existing partitioning
> mechanisms to scale to 100,000 partitions", I could do something like:
>
> Maintain 2 copies of the parent table (partitioned by 256).
> Inherit from both to a relation table.
>
> Does this get me out of the woods with the query analyzer? Doesn't seem
> like it would, necessarily, at least.

You don't get a table's partitions when you inherit.  Just the schema of 
the master.

-- 
--Josh

Josh Berkus
PostgreSQL @ Sun
San Francisco