Re: Separate log for a specfic database

From: Evan Rempel <erempel(at)uvic(dot)ca>
To: pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: Separate log for a specfic database
Date: 2018-02-28 18:17:14
Message-ID: 04ec6db0-2983-1366-ccd6-84e9bbdb21c3@uvic.ca
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On 02/28/2018 10:05 AM, David G. Johnston wrote:
> On Wednesday, February 28, 2018, Ertan Küçükoğlu
> <ertan(dot)kucukoglu(at)1nar(dot)com(dot)tr <mailto:ertan(dot)kucukoglu(at)1nar(dot)com(dot)tr>> wrote:
>
> Hello,
>
> I am using PostgreSQL 9.6.6 on Debian 9 Stretch system. Installed
> using
> apt-get.
> I wonder if I can have two log files. One for complete database
> server and
> another for one specific database in the server.
> I have already read below link, but cannot understand if that is
> possible,
> or how.
> https://www.postgresql.org/docs/9.6/static/runtime-config-logging.html
> <https://www.postgresql.org/docs/9.6/static/runtime-config-logging.html>
>
>
> When it says:
>
> " This parameter can only be set in the postgresql.conf file or on the
> server command line. "
>
> It is scoped to the cluster and all databases therein.  To do what you
> desire you would need to put the unique database into its own cluster.
>
> David J.

That is not exactly true.

Logging could be set up to use syslog and if the database name is in the
log lines
then some filtering and routing of hose messages could go into their own
files.

This would require a mature syslog environment but it is possible.

Evan.

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Rui DeSousa 2018-02-28 18:25:45 Re: Reliable WAL file shipping over unreliable network
Previous Message Rui DeSousa 2018-02-28 18:15:48 Re: Reliable WAL file shipping over unreliable network