| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "postgresql_2016(at)163(dot)com" <postgresql_2016(at)163(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Asia/Jakarta Timezone problem |
| Date: | 2018-05-03 13:37:20 |
| Message-ID: | 5373.1525354640@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
"postgresql_2016(at)163(dot)com" <postgresql_2016(at)163(dot)com> writes:
> 3. Create table, insert timestamp data with WIB or WIT,* failed*.
WIB and WIT aren't in the default list of known timezone abbreviations,
but you can add them in a particular installation easily enough. See
https://www.postgresql.org/docs/10/static/datetime-config-files.html
You could copy the definitions appearing in Asia.txt:
WIB 25200 # Waktu Indonesia Barat
# (Asia/Jakarta)
# (Asia/Pontianak)
WIT 32400 # Waktu Indonesia Timur (caution: this used to mean 25200)
# (Asia/Jayapura)
WITA 28800 # Waktu Indonesia Tengah
# (Asia/Makassar)
Note that which abbreviations are accepted for input has nothing to
do with what you've set "timezone" to.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Clough | 2018-05-03 13:51:04 | RE: postgresql license question |
| Previous Message | postgresql_2016@163.com | 2018-05-03 09:29:35 | Asia/Jakarta Timezone problem |