Tom Lane wrote:
> Christof Petig <[EMAIL PROTECTED]> writes:
> > We noticed that after upgrading to 7.1beta[245] the execution time for
> > some often used queries went up by a factor of 2 or more.
>
> I get the desired plan after doing VACUUM ANALYZE ...
>
> regards, tom
Zeugswetter Andreas SB wrote:
> > Here is one of the queries, it takes about half a second on our computer
> > (PII 233 with 256MB RAM) to execute and returns typically 1-4 rows via
> > two index scans with high selectivity. So it looks to me that planning
> > time outwages execution time by far.
Justin Clift wrote:
> Hi Christof,
>
> I'm not aware of the problem with int2 indexes collapsing. Can you give
> me some more info, and I'll put it on the techdocs.postgresql.org
> website.
Oh, I'm sorry for my strange wording.
I said that the index search collapses to a sequential scan if you
Christof Petig <[EMAIL PROTECTED]> writes:
> We noticed that after upgrading to 7.1beta[245] the execution time for
> some often used queries went up by a factor of 2 or more.
I get the desired plan after doing VACUUM ANALYZE ...
regards, tom lane
---
Justin Clift wrote:
> Hi Christof,
>
> I'm not aware of the problem with int2 indexes collapsing. Can you give
> me some more info, and I'll put it on the techdocs.postgresql.org
> website.
Oh, I'm sorry for my strange wording.
I said that the index search collapses to a sequential scan if you
