Jaime Casanova wrote:
I tried it in two databases (dump and load to another one), so I don't
think that we have corrupted indexes.
the problem persist after a dump a reload? then there is not because
an index corruption... can you send part of the data that reproduces
the bug?
I can try on a newer version of postgresql on another server.
By the way, if this is a bug then it's a serious one. We have it in
production environment.
Mage
what locales do you have? encoding?
The problem can be reproduced on pgsql 8.0.3, compiled from source.
This is a third machine where the bug persists. I dumped the table and
loaded in.
I cannot send the table to you because it contains user data and
passwords. I will try to create a fake one with the same problem.
./configure --prefix=/usr/local/pgsql --with-python
client_encoding | LATIN2
lc_collate | hu_HU
lc_ctype | hu_HU
lc_messages | en_US
lc_monetary | en_US
lc_numeric | en_US
lc_time | en_US
server_encoding | LATIN2
server_version | 8.0.3
Mage
---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings
