SEO

Hi.

I was doing the field test of Slony-I 1.2.2 release now.
However, I encounter the problem of timestamp.:-(
Was anyone recognizing this problem?

Ver 8.1.5
saito=# select 'Fri Dec 15 14:26:05.502000 2006 JST'::timestamp;
timestamp
-------------------------
2006-12-15 14:26:05.502

Ver 8.2.0
saito=# select 'Fri Dec 15 14:26:05.502000 2006 JST'::timestamp;
ERROR: invalid input syntax for type timestamp: "Fri Dec 15 14:26:05.502000 2006 JST"

saito=# select 'Fri Dec 15 14:26:05.502000 2006 GMT'::timestamp;
timestamp
-------------------------
2006-12-15 14:26:05.502


Umm, I might refrain from release for 8.2 of Slony-I for this problem.

Regards,
Hiroshi Saito



---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

On Fri, Dec 15, 2006 at 03:48:50PM +0900, Hiroshi Saito wrote:
> Hi.
>
> I was doing the field test of Slony-I 1.2.2 release now.
> 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.

OTOH, postgres never uses timezone identifiers in output, so I'm not sure
why it would need to care.

Have anice day,
--
Martijn van Oosterhout <kleptog@svana.org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFFgnuUIB7bNG8LQkwRAivUAJwIWrf5dssGC3p4Mlbssn MecVGPEwCfa624
GIN4Tf8W4l0pghlEqKf61KQ=
=MOhX
-----END PGP SIGNATURE-----

----- Original Message -----
From: "Martijn van Oosterhout"
>> I was doing the field test of Slony-I 1.2.2 release now.
>> 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.
>
> OTOH, postgres never uses timezone identifiers in output, so I'm not sure
> why it would need to care.

Thanks.
I do not think that this is normal.....

As for 8.2..
SELECT timeofday()::timestamp;
ERROR: invalid input syntax for type timestamp: "Fri Dec 15 14:26:05.502000 2006 JST"

As for 8.1.5..
SELECT timeofday()::timestamp;

timestamp
-------------------------
2006-12-15 14:26:05.502
(1 row)

Regards,
Hiroshi Saito

---------------------------(end of broadcast)---------------------------
TIP 7: You can help support the PostgreSQL project by donating at

http://www.postgresql.org/about/donate

On Fri, Dec 15, 2006 at 08:20:22PM +0900, Hiroshi Saito wrote:
> Thanks.
> I do not think that this is normal.....
>
> As for 8.2..
> SELECT timeofday()::timestamp;
> ERROR: invalid input syntax for type timestamp: "Fri Dec 15
> 14:26:05.502000 2006 JST"

Err, sounds like a bug to me. Good ahead and file it. Should probably
change the timezone identifier to full form.

Have a nice day,
--
Martijn van Oosterhout <kleptog@svana.org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFFgobAIB7bNG8LQkwRAszKAJ9v4W0ZdHnyWup6TAKe/n4ZixiepwCcDkUO
ICDYIJ9jSjcPkk1/c/l+qUU=
=u5jU
-----END PGP SIGNATURE-----

Martijn van Oosterhout <kleptog@svana.org> writes:
> On Fri, Dec 15, 2006 at 03:48:50PM +0900, Hiroshi Saito wrote:
>> I was doing the field test of Slony-I 1.2.2 release now.
>> 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?

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

Tom Lane <tgl@sss.pgh.pa.us> writes:
> Martijn van Oosterhout <kleptog@svana.org> writes:
>> On Fri, Dec 15, 2006 at 03:48:50PM +0900, Hiroshi Saito wrote:
>>> I was doing the field test of Slony-I 1.2.2 release now.
>>> 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?

Is it absolutely certain that this is missing by default?

Our QA guys were doing some 8.1 work this week, and were griping about
GMT being missing, which turned out to be the result of only part of a
build having been copied into place. (Apparently someone tried saving
space or some such thing; that's definitely a dumb idea!)
--
let name="cbbrowne" and tld="ca.afilias.info" in name ^ "@" ^ tld;;
<http://dba2.int.libertyrms.com/>
Christopher Browne
(416) 673-4124 (land)

---------------------------(end of broadcast)---------------------------
TIP 7: You can help support the PostgreSQL project by donating at

http://www.postgresql.org/about/donate

"Hiroshi Saito" <z-saito@guitar.ocn.ne.jp> writes:
> Hi.
>
> I was doing the field test of Slony-I 1.2.2 release now.
> However, I encounter the problem of timestamp.:-(
> Was anyone recognizing this problem?
>
> Ver 8.1.5
> saito=# select 'Fri Dec 15 14:26:05.502000 2006 JST'::timestamp;
> timestamp
> -------------------------
> 2006-12-15 14:26:05.502
>
> Ver 8.2.0
> saito=# select 'Fri Dec 15 14:26:05.502000 2006 JST'::timestamp;
> ERROR: invalid input syntax for type timestamp: "Fri Dec 15 14:26:05.502000 2006 JST"
>
> saito=# select 'Fri Dec 15 14:26:05.502000 2006 GMT'::timestamp;
> timestamp
> -------------------------
> 2006-12-15 14:26:05.502
>
>
> Umm, I might refrain from release for 8.2 of Slony-I for this problem.

This seems like the well-known issue that if there is some timezone
{unknownzone} that PostgreSQL is unaware of, you oughtn't operate
either Slony-I or PostgreSQL with TZ={unknownzone} or
PGTZ={unknownzone}.

JST strikes me as being a timezone that I'd be a tad surprised for
PostgreSQL NOT to recognize. But that should represent a PostgreSQL
regression problem, not a problem with Slony-I...
--
let name="cbbrowne" and tld="ca.afilias.info" in String.concat "@" [name;tld];;
<http://dba2.int.libertyrms.com/>
Christopher Browne
(416) 673-4124 (land)

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

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...7/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



---------------------------(end of broadcast)---------------------------
TIP 7: You can help support the PostgreSQL project by donating at

http://www.postgresql.org/about/donate

Joachim Wieland <joe@mcknight.de> writes:
> Appended is a patch that adds JST and JDT into Asia.txt and the Default set.

Um ... is there a JDT? Last I heard, Japan does not observe daylight
time. I don't see a JDT in the old PG set of recognized zone names, and
I'd think we'd have heard complaints long ago if it were needed.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

On Fri, Dec 15, 2006 at 11:37:56AM -0500, Tom Lane wrote:
> Joachim Wieland <joe@mcknight.de> writes:
> > Appended is a patch that adds JST and JDT into Asia.txt and the Default set.

> Um ... is there a JDT? Last I heard, Japan does not observe daylight
> time. I don't see a JDT in the old PG set of recognized zone names, and
> I'd think we'd have heard complaints long ago if it were needed.

True... Actually I wonder how I have to read the zic files in this case.
It says:

Rule Japan 1948 only - May Sun>=1 2:00 1:00 D
Rule Japan 1948 1951 - Sep Sat>=8 2:00 0 S
Rule Japan 1949 only - Apr Sun>=1 2:00 1:00 D
Rule Japan 1950 1951 - May Sun>=1 2:00 1:00 D

Zone Asia/Tokyo 9:18:59 - LMT 1887 Dec 31 15:00u
9:00 - JST 1896
9:00 - CJT 1938
9:00 Japan J%sT

The last column of the rules tell us what to put in for %s, but why is there
no

Rule Japan 19xx max .... S

rule? I.e. a rule saying that after some date we should always replace %s
by S? What am I missing here?


Joachim



---------------------------(end of broadcast)---------------------------
TIP 7: You can help support the PostgreSQL project by donating at

http://www.postgresql.org/about/donate