Re: Connection errors in PostgreSQL 9.3.2

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: bricklen <bricklen(at)gmail(dot)com>
Cc: fburgess(at)radiantblue(dot)com, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Connection errors in PostgreSQL 9.3.2
Date: 2014-02-19 23:44:00
Message-ID: 17945.1392853440@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

bricklen <bricklen(at)gmail(dot)com> writes:
> On Wed, Feb 19, 2014 at 2:00 PM, <fburgess(at)radiantblue(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2014-02-20 01:22:13 Re: BUG #9210: PostgreSQL string store bug? not enforce check with correct characterSET/encoding
Previous Message bricklen 2014-02-19 23:07:48 Re: Connection errors in PostgreSQL 9.3.2