Skip site navigation (1) Skip section navigation (2)

Bug #569: Strange Queries Behaviours

From: pgsql-bugs(at)postgresql(dot)org
To: pgsql-bugs(at)postgresql(dot)org
Subject: Bug #569: Strange Queries Behaviours
Date: 2002-01-29 23:20:12
Message-ID: 200201292320.g0TNKC379682@postgresql.org (view raw or flat)
Thread:
Lists: pgsql-bugs
Carlos Atencio (catencio(at)grupozoom(dot)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. The query runs very fast and I get the result I want. Later, I try to reduce the search and instead of list all stores, I want 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 for one store. Accidentally, I made a mistake and wrote the one store sentence twice in that query. My surprise was that the query did work!!!. When the query had the same sentence written twice it actually worked fine and it took fewer time than before.
 
    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


Responses

pgsql-bugs by date

Next:From: Stephan SzaboDate: 2002-01-29 23:37:39
Subject: Re: Bug #569: Strange Queries Behaviours
Previous:From: Carlos AtencioDate: 2002-01-29 22:43:29
Subject: Queries Errors

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group