On Thu, Mar 6, 2014 at 1:26 AM, Pavel Stehule pavel.steh...@gmail.com wrote:
2014-03-05 16:22 GMT+01:00 Alvaro Herrera alvhe...@2ndquadrant.com:
Pavel Stehule escribió:
Hi
I hope, so this patch fix it
wtf?
I tried to fix
2014-03-06 21:06 GMT+01:00 Robert Haas robertmh...@gmail.com:
On Thu, Mar 6, 2014 at 1:26 AM, Pavel Stehule pavel.steh...@gmail.com
wrote:
2014-03-05 16:22 GMT+01:00 Alvaro Herrera alvhe...@2ndquadrant.com:
Pavel Stehule escribió:
Hi
I hope, so this patch fix it
wtf?
I
Hi
I hope, so this patch fix it
Regards
Pavel
2014-03-04 21:00 GMT+01:00 Pavel Stehule pavel.steh...@gmail.com:
2014-03-04 20:20 GMT+01:00 Alvaro Herrera alvhe...@2ndquadrant.com:
Pavel Stehule escribió:
2014-03-04 19:12 GMT+01:00 Alvaro Herrera alvhe...@2ndquadrant.com:
Pavel
Pavel Stehule escribió:
Hi
I hope, so this patch fix it
wtf?
--
Álvaro Herrerahttp://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
2014-03-05 16:22 GMT+01:00 Alvaro Herrera alvhe...@2ndquadrant.com:
Pavel Stehule escribió:
Hi
I hope, so this patch fix it
wtf?
I tried to fix
http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=f1ba94bcd9717b94b36868d6905547e313f3a359
Tom did it better than me.
Pavel Stehule escribió:
Hello
updated version - a precheck is very simple, and I what I tested it is
enough
Okay, thanks. I pushed it after some more editorialization. I don't
think I broke anything, but please have a look.
--
Álvaro Herrerahttp://www.2ndQuadrant.com/
2014-03-04 19:12 GMT+01:00 Alvaro Herrera alvhe...@2ndquadrant.com:
Pavel Stehule escribió:
Hello
updated version - a precheck is very simple, and I what I tested it is
enough
Okay, thanks. I pushed it after some more editorialization. I don't
think I broke anything, but please have
Pavel Stehule escribió:
2014-03-04 19:12 GMT+01:00 Alvaro Herrera alvhe...@2ndquadrant.com:
Pavel Stehule escribió:
Hello
updated version - a precheck is very simple, and I what I tested it is
enough
Okay, thanks. I pushed it after some more editorialization. I don't
think
2014-03-04 20:20 GMT+01:00 Alvaro Herrera alvhe...@2ndquadrant.com:
Pavel Stehule escribió:
2014-03-04 19:12 GMT+01:00 Alvaro Herrera alvhe...@2ndquadrant.com:
Pavel Stehule escribió:
Hello
updated version - a precheck is very simple, and I what I tested it
is
enough
Hello
updated version - a precheck is very simple, and I what I tested it is
enough
Regards
Pavel
2014-02-28 15:11 GMT+01:00 Alvaro Herrera alvhe...@2ndquadrant.com:
Pavel Stehule escribió:
so still I prefer to allow numeric time zones.
What I can:
a) disallow numeric only
2014-02-27 20:10 GMT+01:00 Alvaro Herrera alvhe...@2ndquadrant.com:
Pavel Stehule escribió:
Hello
updated patch without timetz support
Great, thanks.
While testing, I noticed something strange regarding numeric timezone
specification. Basically the way any particular value is handled
Pavel Stehule escribió:
so still I prefer to allow numeric time zones.
What I can:
a) disallow numeric only timezone without prefix + or -
or
b) add + prefix to time zone, when number is possitive.
I prefer @a.
I can live with (a) too. But I wonder if we should restrict the
Hello
updated patch without timetz support
Regards
Pavel
2014-02-19 21:20 GMT+01:00 Alvaro Herrera alvhe...@2ndquadrant.com:
Pavel Stehule escribió:
I though about it, and now I am thinking so timezone in format
'Europe/Prague' is together with time ambiguous
We can do it, but we
Pavel Stehule escribió:
7) Why do the functions accept only the timezone abbreviation, not the
full name? I find it rather confusing, because the 'timezone' option
uses the full name, and we're using this as the default. But doing
'show timestamp' and using the returned value
2014-02-19 19:01 GMT+01:00 Alvaro Herrera alvhe...@2ndquadrant.com:
Pavel Stehule escribió:
7) Why do the functions accept only the timezone abbreviation, not the
full name? I find it rather confusing, because the 'timezone' option
uses the full name, and we're using this as the
2014-02-19 19:01 GMT+01:00 Alvaro Herrera alvhe...@2ndquadrant.com:
Pavel Stehule escribió:
7) Why do the functions accept only the timezone abbreviation, not the
full name? I find it rather confusing, because the 'timezone' option
uses the full name, and we're using this as the
Pavel Stehule escribió:
I though about it, and now I am thinking so timezone in format
'Europe/Prague' is together with time ambiguous
We can do it, but we have to expect so calculation will be related to
current date - and I am not sure if it is correct, because someone can
write some
Dne 19. 2. 2014 21:20 Alvaro Herrera alvhe...@2ndquadrant.com napsal(a):
Pavel Stehule escribió:
I though about it, and now I am thinking so timezone in format
'Europe/Prague' is together with time ambiguous
We can do it, but we have to expect so calculation will be related to
current
Alvaro Herrera alvhe...@2ndquadrant.com writes:
My conclusion here is that the time with time zone datatype is broken
in itself, because of this kind of ambiguity.
That's the conclusion that's been arrived at by pretty much everybody
who's looked at it with any care.
Maybe we should just
Looks good to me.
Regards,
Marko Tiikkaja
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
20 matches
Mail list logo
