You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: archive/en/analyze-table/+comments/feed/index.html
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
<?xml version="1.0" encoding="utf-8"?>
2
-
<rssxmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>MariaDB Knowledge Base Comments for: ANALYZE TABLE</title><link>https://mariadb.com/kb/en/analyze-table/+comments/feed/</link><description></description><atom:linkhref="https://mariadb.com/kb/en/analyze-table/+comments/feed/" rel="self"></atom:link><language>en-us</language><lastBuildDate>Fri, 21 Feb 2025 01:03:17 +0000</lastBuildDate><item><title>Re: ANALYZE TABLE</title><link>https://mariadb.com/kb/en/analyze-table/+comments/7026</link><description><p>Since 10.6.16 there is no blocking or locking with ANALYZE TABLE for any running DML's.</p>
2
+
<rssxmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>MariaDB Knowledge Base Comments for: ANALYZE TABLE</title><link>https://mariadb.com/kb/en/analyze-table/+comments/feed/</link><description></description><atom:linkhref="https://mariadb.com/kb/en/analyze-table/+comments/feed/" rel="self"></atom:link><language>en-us</language><lastBuildDate>Sat, 22 Feb 2025 01:02:12 +0000</lastBuildDate><item><title>Re: ANALYZE TABLE</title><link>https://mariadb.com/kb/en/analyze-table/+comments/7026</link><description><p>Since 10.6.16 there is no blocking or locking with ANALYZE TABLE for any running DML's.</p>
3
3
</description><dc:creatorxmlns:dc="http://purl.org/dc/elements/1.1/">Michael Widenius</dc:creator><guid>https://mariadb.com/kb/en/analyze-table/+comments/7026</guid></item><item><title>Re: ANALYZE TABLE</title><link>https://mariadb.com/kb/en/analyze-table/+comments/7025</link><description><p>This should have been fixed in 10.6.16 and newer versions.
4
4
There should not be any locking or blocking issues after this version.</p>
5
5
</description><dc:creatorxmlns:dc="http://purl.org/dc/elements/1.1/">Michael Widenius</dc:creator><guid>https://mariadb.com/kb/en/analyze-table/+comments/7025</guid></item><item><title>Re: ANALYZE TABLE</title><link>https://mariadb.com/kb/en/analyze-table/+comments/6443</link><description><p>In <a href="/kb/en/what-is-mariadb-104/">Mariadb 10.4</a> EE it caused severe locking issues.
Copy file name to clipboardExpand all lines: archive/en/from_unixtime/+comments/feed/index.html
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
<?xml version="1.0" encoding="utf-8"?>
2
-
<rssxmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>MariaDB Knowledge Base Comments for: FROM_UNIXTIME</title><link>https://mariadb.com/kb/en/from_unixtime/+comments/feed/</link><description></description><atom:linkhref="https://mariadb.com/kb/en/from_unixtime/+comments/feed/" rel="self"></atom:link><language>en-us</language><lastBuildDate>Fri, 21 Feb 2025 01:05:08 +0000</lastBuildDate><item><title>Re: FROM_UNIXTIME</title><link>https://mariadb.com/kb/en/from_unixtime/+comments/5546</link><description><p>Seems like the documentation has an error:</p>
2
+
<rssxmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>MariaDB Knowledge Base Comments for: FROM_UNIXTIME</title><link>https://mariadb.com/kb/en/from_unixtime/+comments/feed/</link><description></description><atom:linkhref="https://mariadb.com/kb/en/from_unixtime/+comments/feed/" rel="self"></atom:link><language>en-us</language><lastBuildDate>Sat, 22 Feb 2025 01:02:28 +0000</lastBuildDate><item><title>Re: FROM_UNIXTIME</title><link>https://mariadb.com/kb/en/from_unixtime/+comments/5546</link><description><p>Seems like the documentation has an error:</p>
3
3
<p>%w =&gt; 0 is Sunday, 6 is Saturday</p>
4
4
</description><dc:creatorxmlns:dc="http://purl.org/dc/elements/1.1/">Bernhard Finkbeiner</dc:creator><guid>https://mariadb.com/kb/en/from_unixtime/+comments/5546</guid></item><item><title>Re: FROM_UNIXTIME</title><link>https://mariadb.com/kb/en/from_unixtime/+comments/4610</link><description><p>It's unlikely - see the note in the article about about using <a href="/kb/en/datetime/">DATETIME</a> instead.</p>
5
5
</description><dc:creatorxmlns:dc="http://purl.org/dc/elements/1.1/">Ian Gilfillan</dc:creator><guid>https://mariadb.com/kb/en/from_unixtime/+comments/4610</guid></item><item><title>Re: FROM_UNIXTIME</title><link>https://mariadb.com/kb/en/from_unixtime/+comments/4608</link><description><p>do exists a possibility that FROM_UNIXTIME will become 64bit?
Returns a representation of the unix_timestamp argument as a value in
354
-
'YYYY-MM-DD HH:MM:SS' or YYYYMMDDHHMMSS.uuuuuu format, depending on
355
-
whether the function is used in a string or numeric context. The value
356
-
is expressed in the current [[time-zones|time zone]]. unix_timestamp is an internal
357
-
timestamp value such as is produced by the [[unix_timestamp|UNIX_TIMESTAMP()]] function.
354
+
Converts the number of seconds from the epoch (1970-01-01 00:00:00 UTC) to a
355
+
##TIMESTAMP## value, the opposite of what ##[[unix_timestamp|UNIX_TIMESTAMP()]]## is doing. Returns NULL if the result would be outside of the valid range of ##TIMESTAMP## values.
358
356
359
-
If format is given, the result is formatted according to the format
360
-
string, which is used the same way as listed in the entry for the
361
-
[[date_format|DATE_FORMAT()]] function.
357
+
If format is given, the result is exactly equivalent to
Before MariaDB 11.7, the one-argument form of ##FROM_UNIXTIME()## was returning a
364
+
##DATETIME##. Meaning, it could return values outside of valid ##TIMESTAMP## range,
365
+
in particular 1970-01-01 00:00:00. And it could return the same result for different values of unix_timestamp (around DST changes).
366
+
<</product>>
362
367
363
368
<<style class="greenbox">>
364
-
Timestamps in MariaDB have a maximum value of 4294967295 (2147483647 before 11.5), equivalent to 2106-02-07 06:28:15 (2038-01-19 05:14:07 before 11.5). This is due to the underlying 32-bit limitation. Using the function on a timestamp beyond this will result in NULL being returned. Use [[datetime|DATETIME]] as a storage type if you require dates beyond this.
369
+
Timestamps in MariaDB have a maximum value of 4294967295, equivalent to 2106-02-07 06:28:15. This is due to the underlying 32-bit limitation. Using the function on a timestamp beyond this will result in NULL being returned. Use [[datetime|DATETIME]] as a storage type if you require dates beyond this.
370
+
<<product mariadb to="11.5">>
371
+
Before MariaDB 11.5, the maximum value was 2147483647, equivalent to 2038-01-19 05:14:07.
372
+
<</product>>
365
373
<</style>>
366
374
367
375
The options that can be used by FROM_UNIXTIME(), as well as [[date_format|DATE_FORMAT()]] and [[str_to_date|STR_TO_DATE()]], are:
Set your time zone to a named time zone to avoid this issue. See [[time-zones/#mysql-time-zone-tables|mysql time zone tables]] for details on how to do this.
<divclass="cstm-style greenbox"><p>Timestamps in MariaDB have a maximum value of 4294967295 (2147483647 before 11.5), equivalent to 2106-02-07 06:28:15 (2038-01-19 05:14:07 before 11.5). This is due to the underlying 32-bit limitation. Using the function on a timestamp beyond this will result in NULL being returned. Use <ahref="/kb/en/datetime/">DATETIME</a> as a storage type if you require dates beyond this.</p>
487
-
</div><p>The options that can be used by FROM_UNIXTIME(), as well as <ahref="/kb/en/date_format/">DATE_FORMAT()</a> and <ahref="/kb/en/str_to_date/">STR_TO_DATE()</a>, are:</p>
489
+
<p>Converts the number of seconds from the epoch (1970-01-01 00:00:00 UTC) to a
490
+
<code>TIMESTAMP</code> value, the opposite of what <code><ahref="/kb/en/unix_timestamp/">UNIX_TIMESTAMP()</a></code> is doing. Returns NULL if the result would be outside of the valid range of <code>TIMESTAMP</code> values.</p>
491
+
<p>If format is given, the result is exactly equivalent to</p>
</pre><divclass="mariadb_to_11_7 mariadb to_11_7 product"><h5class="product_title">MariaDB until <ahref="/kb/en/what-is-mariadb-117/">11.7</a></h5><p>Before <ahref="/kb/en/what-is-mariadb-117/">MariaDB 11.7</a>, the one-argument form of <code>FROM_UNIXTIME()</code> was returning a
494
+
<code>DATETIME</code>. Meaning, it could return values outside of valid <code>TIMESTAMP</code> range,
495
+
in particular 1970-01-01 00:00:00. And it could return the same result for different values of unix_timestamp (around DST changes).</p>
496
+
</div><divclass="cstm-style greenbox"><p>Timestamps in MariaDB have a maximum value of 4294967295, equivalent to 2106-02-07 06:28:15. This is due to the underlying 32-bit limitation. Using the function on a timestamp beyond this will result in NULL being returned. Use <ahref="/kb/en/datetime/">DATETIME</a>as a storage type if you require dates beyond this.</p>
497
+
<divclass="mariadb_to_11_5 mariadb to_11_5 product"><h5class="product_title">MariaDB until <ahref="/kb/en/what-is-mariadb-115/">11.5</a></h5><p>Before <ahref="/kb/en/what-is-mariadb-115/">MariaDB 11.5</a>, the maximum value was 2147483647, equivalent to 2038-01-19 05:14:07.</p>
498
+
</div></div><p>The options that can be used by FROM_UNIXTIME(), as well as <ahref="/kb/en/date_format/">DATE_FORMAT()</a> and <ahref="/kb/en/str_to_date/">STR_TO_DATE()</a>, are:</p>
<tr><td><code>%a</code></td><td>Short weekday name in current locale (Variable <ahref="/kb/en/server-system-variables/#lc_time_names">lc_time_names</a>).</td></tr>
490
501
<tr><td><code>%b</code></td><td>Short form month name in current locale. For locale en_US this is one of: Jan,Feb,Mar,Apr,May,Jun,Jul,Aug,Sep,Oct,Nov or Dec.</td></tr>
<p>If your <ahref="/kb/en/server-system-variables/#time_zone">session time zone</a> is set to <code>SYSTEM</code> (the default), <code>FROM_UNIXTIME()</code> will call the OS function to convert the data using the system time zone. At least on Linux, the corresponding function (<code>localtime_r</code>) uses a global mutex inside glibc that can cause contention under high concurrent load.</p>
527
538
<p>Set your time zone to a named time zone to avoid this issue. See <ahref="/kb/en/time-zones/#mysql-time-zone-tables">mysql time zone tables</a> for details on how to do this.</p>
528
-
<divclass="mariadb_from_11_7 mariadb from_11_7 product"><h5class="product_title">MariaDB starting with <ahref="/kb/en/what-is-mariadb-117/">11.7</a></h5><p>From <ahref="/kb/en/what-is-mariadb-117/">MariaDB 11.7</a>, FROM_UNIXTIME(0) now returns NULL instead of '1970-01-01 00:00:00' (assuming time_zone='+00:00'). See <ahref="https://jira.mariadb.org/browse/MDEV-15751">MDEV-15751</a>.</p>
Copy file name to clipboardExpand all lines: archive/en/mirror-sites-for-mariadb/+comments/feed/index.html
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
<?xml version="1.0" encoding="utf-8"?>
2
-
<rssxmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>MariaDB Knowledge Base Comments for: Mirror Sites for MariaDB</title><link>https://mariadb.com/kb/en/mirror-sites-for-mariadb/+comments/feed/</link><description></description><atom:linkhref="https://mariadb.com/kb/en/mirror-sites-for-mariadb/+comments/feed/" rel="self"></atom:link><language>en-us</language><lastBuildDate>Wed, 19 Feb 2025 01:02:31 +0000</lastBuildDate><item><title>Re: Mirror Sites for MariaDB</title><link>https://mariadb.com/kb/en/mirror-sites-for-mariadb/+comments/4626</link><description><p>Now rsync works fine.
2
+
<rssxmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>MariaDB Knowledge Base Comments for: Mirror Sites for MariaDB</title><link>https://mariadb.com/kb/en/mirror-sites-for-mariadb/+comments/feed/</link><description></description><atom:linkhref="https://mariadb.com/kb/en/mirror-sites-for-mariadb/+comments/feed/" rel="self"></atom:link><language>en-us</language><lastBuildDate>Sat, 22 Feb 2025 01:02:33 +0000</lastBuildDate><item><title>Re: Mirror Sites for MariaDB</title><link>https://mariadb.com/kb/en/mirror-sites-for-mariadb/+comments/4626</link><description><p>Now rsync works fine.
3
3
Thanks for the support.</p>
4
4
</description><dc:creatorxmlns:dc="http://purl.org/dc/elements/1.1/">Daniele Antonini</dc:creator><guid>https://mariadb.com/kb/en/mirror-sites-for-mariadb/+comments/4626</guid></item><item><title>Re: Mirror Sites for MariaDB</title><link>https://mariadb.com/kb/en/mirror-sites-for-mariadb/+comments/4625</link><description><p>This is working again now.</p>
5
5
</description><dc:creatorxmlns:dc="http://purl.org/dc/elements/1.1/">Ian Gilfillan</dc:creator><guid>https://mariadb.com/kb/en/mirror-sites-for-mariadb/+comments/4625</guid></item><item><title>Re: Mirror Sites for MariaDB</title><link>https://mariadb.com/kb/en/mirror-sites-for-mariadb/+comments/4624</link><description><p>This is probably an unintended consequence of some recent changes on the server, we'll look at getting this fixed during the course of the day tomorrow. In the meantime, you can use hasky.askmonty.org as a workaround.</p>
0 commit comments