Thanks Tom. That is what I suspected. I will install the branch tip on
Monday and see if the problem goes away.
Sean
Tom Lane wrote:
Sean Foreman writes:
We recently upgraded postgres from 8.1 to 8.4.
One of our queries stopped working and after some digging I've narrowed
the problem dow
This is not an autocast issue. These are all integers.
The query plan postgres is choosing to execute looks questionable. I
have provided an example of a working query and non-working query. The
change is subtle and takes advantage of the questionable query plan to
get the results I need. The
Sean Foreman writes:
> We recently upgraded postgres from 8.1 to 8.4.
> One of our queries stopped working and after some digging I've narrowed
> the problem down to this:
> select
> count(customer.customer_id)
> from
> acquire.customer customer
> inner join entity_setup.merchant_set
On Thu, Aug 27, 2009 at 2:13 PM, Sean
Foreman wrote:
> We recently upgraded postgres from 8.1 to 8.4.
>
> One of our queries stopped working and after some digging I've narrowed the
> problem down to this:
>
> table structure of interest:
>
> merchant_set
> merchant_set_id
>
> merchant
> merchant_i
There is no error message. Posgres "likes" the query. In this case, the
query returns a count of 1 instead of 3562.
Scott Marlowe wrote:
On Thu, Aug 27, 2009 at 2:13 PM, Sean
Foreman wrote:
We recently upgraded postgres from 8.1 to 8.4.
So, is there an error message you get back? Or
On Thu, Aug 27, 2009 at 2:13 PM, Sean
Foreman wrote:
> We recently upgraded postgres from 8.1 to 8.4.
So, is there an error message you get back? Or just no data?
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
We recently upgraded postgres from 8.1 to 8.4.
One of our queries stopped working and after some digging I've narrowed
the problem down to this:
table structure of interest:
merchant_set
merchant_set_id
merchant
merchant_id
merchant_set_id
customer
customer_id
merchant_set_id
-- failure (c
