From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: rename pg_log directory? |
Date: | 2017-02-28 11:07:06 |
Message-ID: | CABUevEyA7ZWNM1+RK2EEwgPUUEmU0dTZBk6hM-MBOu92bUVW4g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Feb 28, 2017 at 4:01 AM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> On Mon, Feb 27, 2017 at 09:51:26AM -0500, Tom Lane wrote:
> > Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
> > > How about changing the default for log_directory from 'pg_log' to, say,
> > > 'log'?
> >
> > > We have been emphasizing that the prefix "pg_" is for things reserved
> to
> > > PostgreSQL, whereas the pg_log directory is entirely an arbitrary
> > > user-space name. Also, with a different name, the directory would
> stand
> > > out more between all the other pg_* directories in the data directory.
> >
> > No objection to the basic point, but "log" seems perhaps a little too
> > generic to me. Would something like "server_log" be better?
>
> "activity_log"? I like the idea of a rename.
server_log seems like a better choice then I think. So +1 for that.
In theory cluster_log since it's a "cluster level log", but given how many
people already get confused by the term cluster being used that way, I
think that while maybe technically correct, that would be a very bad
choice.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2017-02-28 11:21:01 | Re: Wrong variable type in KeepLogSeg |
Previous Message | Dmitry Dolgov | 2017-02-28 10:59:52 | [PATCH] few fts functions for jsonb |