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

[Debian Bug Tracking System]

Your message dated Mon, 11 Aug 2014 16:08:03 +0200
with message-id <20140811140803.GA1019 at msg.df7cb.de>
and subject line Re: Bug#660649: postgresql-common: postgresql does not log to logfile when log_filename is set
has caused the Debian Bug report #660649,
regarding postgresql-common: postgresql does not log to logfile when log_filename is set
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner at bugs.debian.org
immediately.)


-- 
660649: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660649
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Christoph Anton Mitterer <calestyo at scientia.net>
Subject: postgresql-common: postgresql does not log to logfile when log_filename is set
Date: Mon, 20 Feb 2012 17:16:03 +0100
Size: 2759
URL: <http://lists.alioth.debian.org/pipermail/pkg-postgresql-public/attachments/20140811/91e9a61a/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Christoph Berg <myon at debian.org>
Subject: Re: Bug#660649: postgresql-common: postgresql does not log to logfile when log_filename is set
Date: Mon, 11 Aug 2014 16:08:03 +0200
Size: 2326
URL: <http://lists.alioth.debian.org/pipermail/pkg-postgresql-public/attachments/20140811/91e9a61a/attachment-0001.mht>