Greetings!
Table definitions were included in the original post. I can repost (or
send directly) if desired.
I am using to implement database partitioning based on the day.
Postgresql 8.0.1 (and previous) has a number of issues when it comes to
very large tables. Currently we have anywhere from
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
p
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 , 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, 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.
C
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.
Eugene
--- Edmund Dengler <[EMAIL PROTECTED]> wrote:
>
Greetings all!
Given the quiet, I assume that there is no experience with index issues on
inherited tables? Just seeing if anybody may have any ideas or suggested
work arounds (I seem to have found one by constructing a query that does
all the joins between inherited tables explicitely - this caus
