On Thu, Oct 22, 2009 at 3:46 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Michael Nacos <m.nacos@gmail.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.
I tried to fight the same battle, and apparently this is by design.