[Pkg-postgresql-public] Bug#660649: postgresql-common: postgresql does not log to logfile when log_filename is set

[Adrian Vondendriesch]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I took a look at PgCommon.pm.

If log_filename is set and loggin_collector is off, in
postgresql.conf, pg_ctlcluster assumes that postgresql has set up his
own logfile. Postgres on the other site ignores log_filename because
logging_collector is set to off.

The responsable lines are these:

    # default log file (only if not expliticly configured in
postgresql.conf)
    unless (exists $postgresql_conf{'log_filename'} ||
        exists $postgresql_conf{'log_directory'} ||
        (defined $postgresql_conf{'log_destination'} &&
            $postgresql_conf{'log_destination'} eq 'syslog')) {
        my $log_symlink = $result{'configdir'} . "/log";
        if (-l $log_symlink) {
            ($result{'logfile'}) = readlink ($log_symlink) =~ /(.*)/;
# untaint
        } else {
            $result{'logfile'} =
"/var/log/postgresql/postgresql-$_[0]-$_[1].log";
        }
    }

Regards

	- Adrian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJRkLkYAAoJEJg+KbLX08eJTuMIAIIwlne++k6Qo0sbx8a++0xQ
2fKi22NlVHBgLB3ktBy0nu7yh5q3hmp7EeO0VTGutuuUJJ5qxq7++W/gwdakZxFs
xjXyL2uo7L5AlzdvNNQGxqdzjFeZ79U1X15f0JXE2M6FDjfhShN7mRa0NYgVjjj9
BgRvxKDIJzd3FIrqf+5iwRqC5cGCciYKA0MjzDZOhvpifpBVYcHHB5xjrKfssy5j
qpKlTKaMtHIiToAqrnH0iE30cqbhWXyg+Uje7V6wX6btV+vGauUwCCUZB0OGDszk
5+ne9gpJnplKP8v+NLNIFz8NR7oqHLBAifimqF73yNQTbUsi1RdfzU9iodjvPXo=
=eaCy
-----END PGP SIGNATURE-----