post your table definitions. I suspect you are
indexing the parent table but not the children.
btw, we tried using inherited tables in our
application and quickly found out that they are more
trouble then they are worth (at least the way they are
implemented in postgresql). There are other, more
portable ways of mapping a class hierarchy to
table(s). A few techniques are described in Fowler's
Patterns of Enterprise Application Architecture.
hope this helps,
Eugene
--- Edmund Dengler <edmundd@eSentire.com> wrote:
> Greetings!
>
> I have already increased the stats from 10 to 100.
> In addition, if I
> specify individual tables, then the indexes are
> used. However, when I go
> through the <inherits>, then indexes are not used. I
> will try and expand
> the statistics, but suspect it is not the root cause
> of the problem.
>
> Regards!
> Ed
>
>
> On Tue, 2 Aug 2005, Scott Marlowe wrote:
>
> > On Tue, 2005-08-02 at 16:06, Dr NoName wrote:
> > > The solution to my problem was to increase
> statistics
> > > value and do another analyze. You can also
> change
> > > default_statistics_target parameter in
> > > postgresql.conf. Don't know if that's related to
> the
> > > problem you're seeing, but it's worth a try.
> >
> > Cool postgresql trick:
> >
> > alter database test set
> default_statistics_target=200;
> >
> > You can change the default for a databases's new
> tables too.
> >
> > ---------------------------(end of
> broadcast)---------------------------
> > TIP 2: Don't 'kill -9' the postmaster
> >
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
