>
> I've played around with as many as 1,000 child tables. By then, the
> planning time becomes noticeably longer than for a single table, but
> the response time is still so much faster that it's worth it. Note
> I'm talking only a fraction of a second planning time, even at 1,000
> tables.
>
> If you are going over 100 tables, make sure you're using triggers for
> updating the child tables not rules, as rules are far too slow when
> there's over 50 or so tables to look choose from.
>
> ---------------------------(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- Hide quoted text -
>
> - Show quoted text -
Scott,
Could you share a snippet on how to use trigger for this?
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
