On Oct 2, 1:38 am, rivers.p...@xxxxxxxxx ("paul rivers") wrote:
> > -----Original Message-----
> > From: pgsql-general-ow...@xxxxxxxxxxxxxx [mailto:pgsql-general-
> > ow...@xxxxxxxxxxxxxx] On Behalf Of Goboxe
> > Sent: Monday, October 01, 2007 2:18 AM
> > To: pgsql-gene...@xxxxxxxxxxxxxx
> > Subject: Partitioned table limitation
>
> > Hi,
>
> > Are there any limitations on number of child tables that can be use
> > in
> > partitioned table?
>
> > [snip]
>
> We currently use partitioning by date and id, with 1/4 a year of dates and
> approximately 10 IDs (and slowly increasing). Each partition runs from
> around 1 million to 20 million rows.
>
> Whether it's recommended or not, I don't know. But for us, the partitioning
> works exactly as advertised. As with anything new, I'd take the time to
> setup a simple test to see if it works for you, too.
>
> In particular, be sure to check the documentation on caveats. You'll find
> these a little stricter than partitioning issues in Oracle or SQL Server.
>
> HTH,
> Paul
>
Thanks Paul for your inputs.
I am not really clear when you said "partitioning by date and id, with
1/4 a year of dates and
approximately 10 IDs". Could you give some examples of your tables?
TQ,
G
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
