From: | "tanjunhua" <tanjh(at)riso(dot)co(dot)jp> |
---|---|
To: | "Craig Ringer" <craig(at)postnewspapers(dot)com(dot)au> |
Cc: | "Postgres General Postgres General" <pgsql-general(at)postgresql(dot)org> |
Subject: | ***UNCHECKED*** Re: memory leak occur when disconnect database |
Date: | 2009-07-21 10:39:00 |
Message-ID: | 074401ca09ef$7595b660$aa1c10ac@RKC.local |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I'm sorry for the twice action. because the mail server reject my response.
I should compress it with ciper code(111111) and the execute program is
compressed also.
----- Original Message -----
From: "tanjunhua" <tanjh(at)riso(dot)co(dot)jp>
To: "Craig Ringer" <craig(at)postnewspapers(dot)com(dot)au>
Cc: "Postgres General Postgres General" <pgsql-general(at)postgresql(dot)org>
Sent: Tuesday, July 21, 2009 7:28 PM
Subject: Re: [GENERAL] memory leak occur when disconnect database
>> Please provide full, buildable source code for your standalone test
>> program (or confirm it also occurs with the sources I posted) and the
>> output of:
>>
>> valgrind --leak-check=full ./testprogram
>
> The appendix include source code, execute program and output from top
> command and Valgrind.
> the top_result_before_1_hour is the information got from top command
> before
> executing test program.
> after 1 hour performance, I store the top information into
> top_result_after_1_hour.
> the valgrind_output is the information from Valgrind:
>
> valgrind --leak-check=full show-reachable=yes ./test > valgrind_output
> 2>&1
>
> Best wishes.
>
Attachment | Content-Type | Size |
---|---|---|
memory leak.zip | application/octet-stream | 10.9 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | tanjunhua | 2009-07-21 10:44:32 | ***UNCHECKED*** Re: memory leak occur when disconnect database |
Previous Message | Sam Mason | 2009-07-21 10:35:47 | Re: Best practices for moving UTF8 databases |