Re: leak in libpq, getpwuid

From: Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Michael Nacos <m(dot)nacos(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: leak in libpq, getpwuid
Date: 2009-10-22 15:04:36
Message-ID: 2f4958ff0910220804h20be6f28qf693cd3cbd09c3a3@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Oct 22, 2009 at 3:46 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> 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.
>
> I tried to fight the same battle, and apparently this is by design.

--
GJ

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Michael Nacos 2009-10-22 15:10:39 Re: leak in libpq, getpwuid
Previous Message Tom Lane 2009-10-22 14:46:47 Re: leak in libpq, getpwuid