Re: BUG #2684: Memory leak in libpq
От | Milen A. Radev |
---|---|
Тема | Re: BUG #2684: Memory leak in libpq |
Дата | |
Msg-id | 32c009ea0610101647red19f42pa9a139fce8c1e56a@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: BUG #2684: Memory leak in libpq (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-bugs |
On 10/10/06, Tom Lane <tgl@sss.pgh.pa.us> wrote: > "Milen A. Radev" <milen@radev.net> writes: > > On 10/10/06, Tom Lane <tgl@sss.pgh.pa.us> wrote: > >> I couldn't duplicate any such leak using your test program here. > > > The client and the server were on different machines - that's why I > > believe "md5" was used. I'm sending only the client machine's > > pg_config output. Tell me if you need the server's too. > > I cannot duplicate a leak using a cross-machine connection with md5 > auth, either. I tested this using Fedora Core 5 and the current FC5 > libpq (postgresql-libs-8.1.4-1.FC5.1 RPM). > > I'm wondering if the leak you see is actually the fault of the glibc > version on your machine. You're most probably right - I could reproduce this results only with libc6 2.3.x (Slackware 9.1, Debian stable), but not with version 2.4 (FC5). -- Milen A. Radev
В списке pgsql-bugs по дате отправления: