Michael Nacos <m(dot)nacos(at)gmail(dot)com> writes:
> just to say I have run into related problems on debian lenny amd64 (postgres
> 8.3.5, libc-2.7) and centos 5.2 (postgres 8.4.1, libc-2.5)
This is not a Postgres bug. You can try filing it against glibc, but
I wouldn't be too surprised if they tell you it's not worth fixing.
regards, tom lane