pgsql: Fix memory leak in syslogger: logfile_rotate() would leak a copy - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: Fix memory leak in syslogger: logfile_rotate() would leak a copy
Date
Msg-id 20091119024540.8A9A1753FB7@cvs.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Fix memory leak in syslogger: logfile_rotate() would leak a copy of the
output filename if CSV logging was enabled and only one of the two possible
output files got rotated during a particular call (which would, in fact,
typically be the case during a size-based rotation).  This would amount to
about MAXPGPATH (1KB) per rotation, and it's been there since the CSV
code was put in, so it's surprising that nobody noticed it before.
Per bug #5196 from Thomas Poindessous.

Tags:
----
REL8_4_STABLE

Modified Files:
--------------
    pgsql/src/backend/postmaster:
        syslogger.c (r1.51 -> r1.51.2.1)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/postmaster/syslogger.c?r1=1.51&r2=1.51.2.1)

pgsql-committers by date:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Fix memory leak in syslogger: logfile_rotate() would leak a copy
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Fix memory leak in syslogger: logfile_rotate() would leak a copy