Shreeyansh, Scott,
Thanks for responding. Here’s the value of a couple log parms
gp07> psql -d postgres -c"show log_file_mode"
log_file_mode
---------------
0600
(1 row)
gp07> psql -d postgres -c"show log_filename"
log_filename
---------------
gp07error.log
(1 row)
gp07> psql -d postgres -c"show logging_collector"
logging_collector
-------------------
on
(1 row)
Also, we have a monitor that checks the errorlog. This monitor appends the current log to an archive file (example, errorlog.201503), then touch a new ‘error.log’. After the touch, the new errorlog is not written to anymore, until postgres is bounced. I should also note that new error.log is owned by the monitor ID:
-rw-rw-r-- 1 psgdba dbagroup 298 Mar 13 05:43 gl07error.log
dbagroup members are: psgdba and instance-owner.
Thanks.
Maria A Rossi
Database Administration
PGDS (US)
email: maria.rossi@us.pgds.com
cell phone: 517.256.4392
work phone: 517.367.3099
work phone extension: 23099
From: Shreeyansh Dba [mailto:shreeyansh2014@gmail.com]
Sent: Friday, March 13, 2015 1:14 AM
To: Scott Ribe
Cc: Rossi, Maria; Postgres Maillist
Subject: Re: [ADMIN] Errorlog empty
On Thu, Mar 12, 2015 at 11:09 PM, Scott Ribe <scott_ribe@elevated-dev.com> wrote:
On Mar 12, 2015, at 11:12 AM, Rossi, Maria <maria.rossi@us.pgds.com> wrote:
>
> Igor,
>
> Here's the other 'log' configs: Thanks.
>
> postgres=# show log_destination;
> log_destination
> -----------------
> stderr
> (1 row)
>
> postgres=# show log_filename;
> log_filename
> ---------------
> gp07error.log
> (1 row)
>
> postgres=# show log_directory;
> log_directory
> -----------------------------
> /dba/pgsql/gp07/pg_errorlog
> (1 row)
>
> postgres=# show log_connections;
> log_connections
> -----------------
> on
> (1 row)
>
> postgres=# show log_disconnections;
> log_disconnections
> --------------------
> on
> (1 row)
>
What about logging_collector? If that's not set, I think your log filename will be ignored and messages will go to stderr. See: <http://www.postgresql.org/docs/9.4/static/runtime-config-logging.html>
--
Scott Ribe
scott_ribe@elevated-dev.com
http://www.elevated-dev.com/
(303) 722-0567 voice
Reload is fine no need to restart.
you can check whether parameters are configured using
May be there some permission issue to the log_destination folder.So once check the permissions and
Try
log_filename = 'postgresql-%Y-%m-%d_%H%M%S.log'
And let me know the output.