[pgpool-general: 178] Re: Fwd: Pgpool 3.1.1: possible memory leak
ishii at postgresql.org
Wed Jan 18 15:40:59 JST 2012
Thanks for the report. It's definitely interesting:-)
SRA OSS, Inc. Japan
> Hi Tatsuo.
> I think i found the problem. Our packaging routine was downloading a 3.1.1 version from http://pgfoundry.org/frs/download.php/3114/pgpool-II-3.1.1.tar.gz which doesn't exist (interestingly enough pgfoundry returns pgpool-II-3.1 for download using that url).
> I modified the routine to download from http://www.pgpool.net/mediawiki/index.php/Downloads and now all I don't have memory leaks anymore.
> Thank you and sorry for the noise.
> ----- Messaggio originale -----
>> Da: "Denis Gasparin" <denis.gasparin at edistar.com>
>> A: "Tatsuo Ishii" <ishii at postgresql.org>
>> Cc: pgpool-general at pgpool.net
>> Inviato: Lunedì, 16 gennaio 2012 14:04:16
>> Oggetto: [pgpool-general: 169] Re: Fwd: Pgpool 3.1.1: possible memory leak
>> Il giorno 16/gen/2012, alle ore 13:03, Tatsuo Ishii
>> <ishii at postgresql.org> ha scritto:
>> >> The socket directories are different:
>> >> # Unix domain socket path. (The Debian package defaults to
>> >> # /var/run/postgresql.)
>> >> socket_dir = '/var/run/'
>> >> # Unix domain socket path for pgpool communication manager.
>> >> # (Debian package defaults to /var/run/postgresql)
>> >> pcp_socket_dir = '/var/run/pgpool/pcp/'
>> >> I tried setting two different ports (127001 and 127002) but the
>> >> memory leak still remains.
>> > Oh, ok. How many times did you do insertion before you see memory
>> > leak? I tried with 384 insertions in my environment and see no leak.
>> I see the leak after few iterations (10).
>> We connect pgpool to an 8.2 postgres and we compiled pgpool in a suse
>> Could i give you any other info in order to debug the leak?
>> Thank you,
>> pgpool-general mailing list
>> pgpool-general at pgpool.net
More information about the pgpool-general