Sorry for a late reply, but I had the exact same problem and it was a bug
in the Red Hat RPM package upgrade script of the sudo package. This
basically means the user running Postgres cannot resolve hostname
localhost. Have you tried logging in as the user running Postgres and
trying to resolve loc
Kong Man wrote:
> The postgresql.conf file has always been using the default value, which is
> 'warning'.
Maybe it's not using the postgresql.conf file you think it is. Does
this show the file you've been looking at?:
SHOW config_file;
-Kevin
--
Sent via pgsql-admin mailing list (pgsql-admi
On Sun, 23 Dec 2012 11:08:32 -0500, Kevin Grittner wrote:
> Kong Man wrote:
>
>> The postgresql.conf file has always been using the default value, which
>> is 'warning'.
>
> Maybe it's not using the postgresql.conf file you think it is. Does this
> show the file you've been looking at?:
>
> SHO
Kong Man writes:
> We ran into a production issue during our maintenance window when I switched
> over LifeKeeper/PostgreSQL nodes from one to another. We noticed that the
> database was 1000 times slower than it usually is, then realized that the
> log_min_messages setting was set to 'debug5'
Hi Tom,
Thank you for some clue in this. So, I assume changing log_destination (from
syslog to stderr) was a way around it to override log_min_messages when the -d
option is specified?
I am checking with the vender, SIOS, on what scenarios LifeKeeper would start
up PostgreSQL with the -d5 op
