On 01/28/2013 10:38 AM, Anson Abraham wrote:
no cluster, just 2 different independent/isolated DB servers.
On the same machine or different machines?
As for location of logs, yes, it's the correct one, b/c when logrotate
(through system), initiated I can see the other log files gzipped. The
no cluster, just 2 different independent/isolated DB servers.
As for location of logs, yes, it's the correct one, b/c when logrotate
(through system), initiated I can see the other log files gzipped. The
install was done through ,what I believe, apt-get.
I guess it might require a bouncing of the
On 01/25/2013 09:00 AM, Anson Abraham wrote:
identical.
This is on Debian correct?
Are you using the Debian pg_cluster system?
In particular are using pg_ctlcluster to start the server?
From what I remember of pg cluster is that the init.d script is called
by pg_ctlcluster and the pg_ctclust
I though to do that w/ log_destination, but i left everything pretty much
default except those params I mentioned earlier.
Interestingly i have another DB server (same ver, etc...) w/ exact same
config params w/ postgres and sys log config and that is writing to the
"system postgres log".
it's a
On 01/24/2013 01:38 PM, Anson Abraham wrote:
I though to do that w/ log_destination, but i left everything pretty
much default except those params I mentioned earlier.
Interestingly i have another DB server (same ver, etc...) w/ exact same
config params w/ postgres and sys log config and that is
On 01/24/2013 12:44 PM, Anson Abraham wrote:
i've always had logging_collector off. it would still log query /
transactions that failed to the "syslog"
(var/log/postgres/postgres-9.0-main.log).
the only thing I've changed was turning log_duration back to off. But
I've gone back and forth with w
On 01/24/2013 10:36 AM, Anson Abraham wrote:
#log_destination = 'stderr'
#logging_collector = off
It was when it was restarted that this didn't start logging. To restart
is an option, but one I'd like to avoid.
It's 9.0 on debian squeeze.
init.d/postgres start
It was writing before. Just sto
#log_destination = 'stderr'
#logging_collector = off
It was when it was restarted that this didn't start logging. To restart is
an option, but one I'd like to avoid.
It's 9.0 on debian squeeze.
init.d/postgres start
It was writing before. Just stopped after the last restart or rather
reload of
On 01/24/2013 09:29 AM, Anson Abraham wrote:
my postgresql-9.0-main.log log file is 0 bytes. Postgres user has perms
to write to it. And and postgresql.conf file shows to log, but it's
not. Not sure why.
I have the defaults set in except for these changes:
log_connections = on
log_disconnect
