Is MySQL on each one set to the same time zone?
SELECT@@global.time_zone;
-Ryan
Néstor wrote:
> That was interesting. I have 2 rhel 3 servers and they both have been
> update to handle the DST. They both yield different results when I
> ran the
> command:
> SERVER=RALPH
> +---------------------------------------+---------------------------------------+
>
> | UNIX_TIMESTAMP('2007-03-11 02:00:00') | UNIX_TIMESTAMP('2007-03-11
> 03:00:00') |
> +---------------------------------------+---------------------------------------+
>
> | 1173607200 | 1173610800 |
> +---------------------------------------+---------------------------------------
>
>
>
> and this for the other server :
> SERVER=MAGGIE
> +---------------------------------------+---------------------------------------+
>
> | UNIX_TIMESTAMP('2007-03-11 02:00:00') | UNIX_TIMESTAMP('2007-03-11
> 03:00:00') |
> +---------------------------------------+---------------------------------------+
>
> | 1173607200 | 1173607200 |
> +---------------------------------------+---------------------------------------
>
>
>
> Uhmmmmm.............
>
>
> Nestor
>
> On 2/28/07, William R. Mussatto <mussatto@stripped> wrote:
>>
>> On Wed, February 28, 2007 14:10, Ryan Stille said:
>> > I am on 4.1.20-1.
>> >
>> > Maybe your OS isn't patched?
>> >
>> > Try this: "SELECT @@global.time_zone;"
>> Won't help if you are on debian which is still on 4.0.
>> > If you get back "SYSTEM", then MySQL is looking to the OS for timezone
>> > data. And its only loaded when MySQL starts, so if you haven't
>> > restarted MySQL since you patched your OS, you need to do that.
>> >
>> > -Ryan
>> >
>> > Jerry Schwartz wrote:
>> >> What version of MySQL are you using? I'm running 4.1.21, and that
>> check
>> >> doesn't work even after I've updated (I think) the time zone tables.
>> >>
>> >> I should probably eyeball the output of mysql_tzinfo_to_sql.
>> >>
>> >> Regards,
>> >>
>> >> Jerry Schwartz
>> >> Global Information Incorporated
>> >> 195 Farmington Ave.
>> >> Farmington, CT 06032
>> >>
>> >> 860.674.8796 / FAX: 860.674.8341
>> >>
>> >>
>> >>
>> >>> -----Original Message-----
>> >>> From: Ryan Stille [mailto:ryan@stripped]
>> >>> Sent: Saturday, February 24, 2007 4:28 PM
>> >>> To: mysql@stripped
>> >>> Subject: Re: MySQL Daylight Savings Time Patch - easy check
>> >>>
>> >>> Ryan Stille wrote:
>> >>>
>> >>>> Paul DuBois wrote:
>> >>>>
>> >>>>> At 4:40 PM -0600 2/20/07, Ryan Stille wrote:
>> >>>>>
>> >>>>>> Is there an easy way to test to see if MySQL already
> has
>> >>>>>>
>> >>> the proper
>> >>>
>> >>>>>> tables loaded?
>> >>>>>>
>> >>>>>> -Ryan
>> >>>>>>
>> >>>>> Yes, reload them. :-) After that, they're current! .......
>> >>>>>
>> >>>>>
>> >>> After digging around on the net for a while I found an easy
>> >>> way to tell
>> >>> if your MySQL installation is ready for the new daylight savings
>> time.
>> >>>
>> >>> SELECT UNIX_TIMESTAMP('2007-03-11 02:00:00'),
>> >>> UNIX_TIMESTAMP('2007-03-11 03:00:00');
>> >>>
>> >>> This should return the same value, even though you are feeding it
>> >>> different times, because this is when the 1 hr change occurs.
>> >>> I get the
>> >>> correct result on both of my machines. On one of them I've run the
>> >>> suggested |mysql_tzinfo_to_sql command, on the other, the time zone
>> >>> tables are completely empty!
>> >>>
>> >>> Any wisdom on these time zone tables - are they ever used, should I
>> >>> populate them or not?
>> >>>
>> >>> -Ryan
>> >>>
>> >>> |
>> >>>
>> >>>
>> >>> --
>> >>> MySQL General Mailing List
>> >>> For list archives: http://lists.mysql.com/mysql
>> >>> To unsubscribe:
>> >>> http://lists.mysql.com/mysql?unsub=1
>> >>>
>> >>>
>> >>>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >
>> >
>> >
>> > --
>> > MySQL General Mailing List
>> > For list archives: http://lists.mysql.com/mysql
>> > To unsubscribe: http://lists.mysql.com/mysql?unsub=1
>> >
>> >
>>
>>
>>
>> --
>> MySQL General Mailing List
>> For list archives: http://lists.mysql.com/mysql
>> To unsubscribe: http://lists.mysql.com/mysql?unsub=1
>>
>>
>
