Andomar writes:
> Thanks for your reply, log_destination is set to "stderr". And
> logging_collector is "on".
> On CentOS, this results in regular Postgres log files. On Arch Linux,
> the results end up in the system journal. It looks like the Postgres
> logging collector somehow misses out
On 07/01/2015 05:26 AM, Andomar wrote:
are you just missing this parameter:
#log_destination = 'stderr' # Valid values are
combinations of
# stderr, csvlog, syslog, and
eventlog,
# depending on platform
On 07/01/2015 12:22 AM, Andomar wrote:
In Arch Linux, Postgres is started by systemd. If you configure
logging_collector in postgresql.conf this has no effect. All of the logging
output is send to the journal, where you can read it with “journalctl -u
postgresql”.
The configuration for system
are you just missing this parameter:
#log_destination = 'stderr' # Valid values are combinations of
# stderr, csvlog, syslog, and eventlog,
# depending on platform. csvlog
> -Original Message-
> From: pgsql-general-ow...@postgresql.org [mailto:pgsql-general-
> ow...@postgresql.org] On Behalf Of Andomar
> Sent: Mittwoch, 1. Juli 2015 09:22
> To: pgsql-general@postgresql.org
> Subject: [GENERAL] Systemd vs logging collector
>
> In
In Arch Linux, Postgres is started by systemd. If you configure
logging_collector in postgresql.conf this has no effect. All of the logging
output is send to the journal, where you can read it with “journalctl -u
postgresql”.
The configuration for systemd contains a StandardError option. I’ve t
