| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | chris(dot)travers(at)gmail(dot)com |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #8170: alter user does not accept timestamp output format in certain datestyles and timezones. |
| Date: | 2013-05-20 13:06:18 |
| Message-ID: | 3193.1369055178@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
chris(dot)travers(at)gmail(dot)com writes:
> db=# show timezone;
> TimeZone
> --------------
> Asia/Jakarta
> (1 row)
> db=# select now();
> now
> -------------------------------------
> Mon 20 May 11:39:24.273508 2013 WIT
> (1 row)
> db=# ALTER USER chris with valid until 'Tue 21 May 11:41:14.58554 2013 WIT';
> ERROR: invalid input syntax for type timestamp with time zone: "Tue 21 May
> 11:41:14.58554 2013 WIT"
> This worked before with different timezones with the same datestyle. Why is
> this failing?
You need to add WIT to the timezone abbreviation list to allow it to be
used as input:
http://www.postgresql.org/docs/9.2/static/datetime-config-files.html
Or perhaps better, use the ISO datestyle to eliminate the whole issue of
timezone abbreviations.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrzej Cedro | 2013-05-21 06:54:09 | Re: BUG #7659: LDAP auth does not search the subtree |
| Previous Message | Trond.Endrestol | 2013-05-20 07:32:55 | BUG #8171: Log messages lacking enough details |