| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Dev Kumkar <devdas(dot)kumkar(at)gmail(dot)com> |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, Andrew Sullivan <ajs(at)crankycanuck(dot)ca>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Timezone information |
| Date: | 2014-02-19 22:27:53 |
| Message-ID: | 16435.1392848873@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Dev Kumkar <devdas(dot)kumkar(at)gmail(dot)com> writes:
> On Thu, Feb 20, 2014 at 3:07 AM, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>wrote:
>> Do you know where the machine is going when you do the install?
> No if that was the case then target could have set before shipping itself.
> Machine TGT-Region is not known here.
The functionality of determining an IANA timezone name equivalent to the
platform's behavior is currently embedded in initdb and isn't separately
accessible. So you've got several options:
1. Wait to do initdb until the machine is installed.
2. Modify the timezone setting in postgresql.conf after the machine is
installed (although there might not be an easy way to determine what
to set it to).
3. Leave the server timezone setting as GMT and rely on clients to select
the zone they want to work in.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2014-02-19 23:01:53 | Re: Timezone information |
| Previous Message | Terence Ferraro | 2014-02-19 22:25:43 | Re: Timezone information |