Re: invalid input syntax for type timestamp.

From: Joachim Wieland <joe(at)mcknight(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Martijn van Oosterhout <kleptog(at)svana(dot)org>, Hiroshi Saito <z-saito(at)guitar(dot)ocn(dot)ne(dot)jp>, pgsql-hackers(at)postgresql(dot)org, Devrim GUNDUZ <devrim(at)commandprompt(dot)com>, Christopher Browne <cbbrowne(at)ca(dot)afilias(dot)info>
Subject: Re: invalid input syntax for type timestamp.
Date: 2006-12-15 16:30:36
Message-ID: 20061215163036.GA3775@mcknight.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Dec 15, 2006 at 10:17:20AM -0500, Tom Lane wrote:
> >> However, I encounter the problem of timestamp.:-(
> >> Was anyone recognizing this problem?

> > The list of accepted timezones is now configurable, check through the
> > docs how to find the list and set it the way you want.

> Yeah, but why the heck isn't JST in it by default? This seems to have
> slipped through the cracks, because I don't see it anywhere in any of
> the timezonesets/* files. Joachim?

Yes, it got removed, see

http://archives.postgresql.org/pgsql-patches/2006-07/msg00077.php

I checked each of the timezones I removed but I don't have my notes anymore
as to why I thought JST could be removed. Obviously, it shouldn't be
removed...

Appended is a patch that adds JST and JDT into Asia.txt and the Default set.

Joachim

Attachment Content-Type Size
jst-jdt.diff text/plain 1.5 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-12-15 16:37:56 Re: invalid input syntax for type timestamp.
Previous Message Dave Page 2006-12-15 16:26:07 Re: libpq.a in a universal binary