Обсуждение: BUG #4073: ERROR: invalid input syntax for type timestamp: "Sat Mar 29 04:47:06 WEST 2008"

The following bug has been logged online:

Bug reference:      4073
Logged by:          Pedro Alves
Email address:      pedro@neraka.no-ip.org
PostgreSQL version: 8.2.7
Operating system:   Linux Slackware 11 and 12
Description:        ERROR:  invalid input syntax for type timestamp: "Sat
Mar 29 04:47:06 WEST 2008"
Details:

Since saturday Portugal is in WEST timezone. Some of my programs stopped
working. Those programs use the output of java.util.Date, and come out as
"Sat Mar 29 04:47:06 WEST 2008".


Though not everyone uses that kind of output in timezones, everyone that
uses a recent jvm and are in portugal, faroe island or canary island will
have issues with this. Ref:
http://www.timeanddate.com/library/abbreviations/timezones/eu/west.html


I found a way to *hack* the solution by copying the file Portugal to WEST in
share/timezones

Thanks

Pedro Alves wrote:
> Since saturday Portugal is in WEST timezone. Some of my programs stopped
> working. Those programs use the output of java.util.Date, and come out as
> "Sat Mar 29 04:47:06 WEST 2008".
>
> Though not everyone uses that kind of output in timezones, everyone that
> uses a recent jvm and are in portugal, faroe island or canary island will
> have issues with this. Ref:
> http://www.timeanddate.com/library/abbreviations/timezones/eu/west.html

We don't include all timezone abbreviations, because they're generally
not well-defined. Not sure if that's the case with WEST, but it seems
quite likely. We do have the abbreviation WETDST for that, though.

> I found a way to *hack* the solution by copying the file Portugal to WEST in
> share/timezones

No need for such hacks, see:

http://www.postgresql.org/docs/8.3/interactive/datetime-config-files.html

--
   Heikki Linnakangas
   EnterpriseDB   http://www.enterprisedb.com

Heikki Linnakangas <heikki@enterprisedb.com> writes:
> Pedro Alves wrote:
>> Since saturday Portugal is in WEST timezone.

> We don't include all timezone abbreviations, because they're generally
> not well-defined. Not sure if that's the case with WEST, but it seems
> quite likely. We do have the abbreviation WETDST for that, though.

Yeah, it seems to have been left out of our default list of TZ
abbreviations, probably because it seemed way too likely to be
non-unique.

            regards, tom lane