Skip site navigation (1) Skip section navigation (2)

Re: Monitoring with pg_controldata

From: Tim Uckun <timuckun(at)gmail(dot)com>
To: "Uwe C(dot) Schroeder" <uwe(at)oss4u(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Monitoring with pg_controldata
Date: 2009-07-30 01:53:18
Message-ID: 855e4dcf0907291853m79250efcm592280bc867368e3@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-general
O
> cron runs programs in a very limited environment. Things like TZ etc. are
> usually not set. To see what your cron sets, just run a shell script with
> something like
>
> #!/bin/sh
> env
>
> and look at the email you get with the output.
> Read the cron/crontab manpage. It tells you how to set environment variables
> for your scripts.


Thanks for the tip. It looks like the LANG environment wasn't set and
obviously pg_controldata is reliant on that.  What solved it for me
was to set LANG=en_GB.UTF-8 because that was the LANG setting in the
postgres user env.

Thanks again.

In response to

pgsql-general by date

Next:From: Alan DeaneDate: 2009-07-30 02:00:11
Subject: Re: V8.3 fails to start after unremming hba_file = 'ConfigDir/pg_hba.conf'
Previous:From: Brodie ThiesfieldDate: 2009-07-30 01:53:11
Subject: Re: How to prevent duplicate key error when two processes do DELETE/INSERT simultaneously?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group