Re: main.log file not being updated

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 instance, but that's something I
don't have luxury of doing until the next maintanence window, which will be
a ways in the future.

Thanks,
-Anson

On Fri, Jan 25, 2013 at 3:35 PM, Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>wrote:

> 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_ctcluster code takes care of setting up the
> logging to the appropriate log in /var/log/postgres. If you call the init
> script directly it just follows whatever are the settings in
> postgresql.conf, which in your case would not actually log anything.
>
>
> Another possibility.
> Are you sure you are looking at the correct log?
> One of the features of pg cluster is that there can be multiple versions
> of Postgres and multiple db clusters in a version. Again if I remember
> correctly main is the default cluster for a version.
>
> Is it possible there is another cluster running PG 9.0?
>
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)gmail(dot)com
>