Bug #569: Strange Queries Behaviours - Mailing list pgsql-bugs

From pgsql-bugs@postgresql.org
Subject Bug #569: Strange Queries Behaviours
Date
Msg-id 200201292320.g0TNKC379682@postgresql.org
Whole thread Raw
Responses Re: Bug #569: Strange Queries Behaviours  (Stephan Szabo <sszabo@megazone23.bigpanda.com>)
List pgsql-bugs
Carlos Atencio (catencio@grupozoom.com) reports a bug with a severity of 2
The lower the number the more severe it is.

Short Description
Strange Queries Behaviours

Long Description
Hi,

    I've installed Postgres 7.0.3.
    The bug I founded was very weird.

    I've this query that I run in my app. For example, give a list of all sales from all my stores around the country.
Thequery runs very fast and I get the result I want. Later, I try to reduce the search and instead of list all stores,
Iwant to list only one store. The query runs but this time is slower than before (I have the proper indexes in that
table).In this case, we're using the same query but with one more condition. 

    I looked at the query with the explain command and I saw that Postgres wasn't using the sentence where I ask only
forone store. Accidentally, I made a mistake and wrote the one store sentence twice in that query. My surprise was that
thequery did work!!!. When the query had the same sentence written twice it actually worked fine and it took fewer time
thanbefore. 

    None has known how to repair this. In some queries, duplicating some senteces makes it work. In other queries, it
doesn't.

Please, if you know how to correct this let me know.

Carlos E.Atencio
Caracas-Venezuela


Sample Code


No file was uploaded with this report

pgsql-bugs by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: no data for locks
Next
From: Stephan Szabo
Date:
Subject: Re: Bug #569: Strange Queries Behaviours