Hi Bill,
In response to Arnau <arnaulist@xxxxxxxxxxxxxxxxxx>:
I have postgresql 7.4.2 running on debian and I have the oddest
postgresql behaviour I've ever seen.
I do the following queries:
espsm_asme=# select customer_app_config_id, customer_app_config_name
from customer_app_config where customer_app_config_id = 5929 or
customer_app_config_id = 11527 order by customer_app_config_id;
customer_app_config_id | customer_app_config_name
------------------------+--------------------------
5929 | INFO
(1 row)
I do the same query but changing the order of the or conditions:
espsm_asme=# select customer_app_config_id, customer_app_config_name
from customer_app_config where customer_app_config_id = 11527 or
customer_app_config_id = 5929 order by customer_app_config_id;
customer_app_config_id | customer_app_config_name
------------------------+--------------------------
11527 | MOVIDOSERENA TONI 5523
(1 row)
As you can see, the configuration 5929 and 11527 both exists, but
when I do the queries they don't appear.
[snip]
Just a guess, but perhaps your index is damaged. Have you tried
REINDEXing?
Yes, I have tried with:
reindex table customer_app_config
reindex index pk_cag_customer_application_id
but nothing changed. I also tried to drop the index:
espsm_asme=# begin; drop index pk_cag_customer_application_id;
BEGIN
ERROR: cannot drop index pk_cag_customer_application_id because
constraint pk_cag_customer_application_id on table customer_app_config
requires it
HINT: You may drop constraint pk_cag_customer_application_id on table
customer_app_config instead.
espsm_asme=# rollback;
ROLLBACK
But I can't remove the constraint as it's the primary key and there
are foreign keys over it
--
Arnau
