Comment 1 for bug 1026055

Seems like the bug Viktor found in PostgreSQL itself: http://archives.postgresql.org/message-id/20120706184951.GA91000%40client195-161.wlan.hu-berlin.de

This was fixed in PostgreSQL itself (http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=628cbb50ba80c83917b07a7609ddec12cda172d0) and will be backported to 8.4 (http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=b9edaa784e407d1b6e890b776c607a26f3aa7e49) and 9.1 (http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=a9287de1760450e7fe3b4309ee1ba7ea2af39217)

We should wait for the official releases and if this fixes the problem make a public anouncement to upgrade.