| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Majid Azimi <majid(dot)merkava(at)gmail(dot)com> |
| Cc: | pgsql-novice <pgsql-novice(at)postgresql(dot)org> |
| Subject: | Re: TimeZone parameter in postgresql.conf |
| Date: | 2012-09-06 00:48:27 |
| Message-ID: | 1346892507.4708.1.camel@sussancws0025 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
On Wed, 2012-09-05 at 22:33 +0430, Majid Azimi wrote:
> postgresql documentation says:
>
> All timezone-aware dates and times are stored internally in
> UTC. They are converted to local time in the zone specified by
> the timezone configuration parameter before being displayed to
> the client.
>
>
> timezone parameter is a session parameter. When all TIMESTAMP WITH
> TIME ZONEs will be stored as UTC and the client connection will
> specify the session timezone, then what is the benefit of setting
> TimeZone parameter in postgresql.conf?
It's essentially just a default so that you don't have to specify it in
the session.
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Davidson | 2012-09-06 17:57:07 | On naming of executables |
| Previous Message | lmanorders | 2012-09-05 22:35:26 | Re: How to determine if a function exists |