There are 260 entries in the /opt/PostgreSQL/9.3/share/postgresql/timezone directory.

There are 252 entries in our old obsolete PostgreSQL 9.1.6 /opt/PostgreSQL/9.1/share/postgresql/timezone directory.

I checked the permissions in the /opt/PostgreSQL/9.3/share/postgresql/timezone and they were set to 600. I cross-checked these against a 9.1 instance we have running on another box and the permissions were 644 could this be the issue?

thanks

-------- Original Message --------
Subject: Re: [BUGS] Connection errors in PostgreSQL 9.3.2
From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Wed, February 19, 2014 4:44 pm
To: bricklen <bricklen@gmail.com>
Cc: fburgess@radiantblue.com, pgsql-bugs@postgresql.org

bricklen <bricklen@gmail.com> writes:
> On Wed, Feb 19, 2014 at 2:00 PM, <fburgess@radiantblue.com> wrote:
>> We are getting the following error trying to connect to PostgreSQL even
>> though I commented out the *timezone* and *log_timezone* settings in the
>> postgresql.conf file.
>> *Invalid value for parameter "Timezone": "Etc/GMT"*
>> Does anyone know how to fix this?

> Did you reload the postgresql.conf file after the change? If so, perhaps it
> is set at the role level? What does the following show: "select
> rolname,rolconfig from pg_roles;"

If the complaint is showing up at connection time then the setting is not
coming from postgresql.conf. Aside from role or database settings, it
could be that the client side is trying to set it (perhaps due to a PGTZ
environment variable).

The other angle that is worth considering is why isn't that value
considered valid? It works for me. Perhaps you have an incomplete
share/timezone directory, or if you built with --with-system-tzdata,
maybe the directory that points to is incomplete.

regards, tom lane


--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs