mir/kea
2
0
Fork 0
mirror of https://gitlab.isc.org/isc-projects/kea synced 2025-08-31 22:15:23 +00:00
Code Issues Releases Wiki Activity

[3673] Updated Kea guide with the limitations for the SQL timestamps.

Browse Source
This commit is contained in:
Marcin Siodelski
2015-03-11 21:17:09 +01:00
parent f48f9ebae5
commit efe7294639
1 changed files with 16 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
doc/guide/admin.xml
View File

@@ -432,6 +432,22 @@ host <replaceable>database-name</replaceable> <replaceable>user-name</repl
<!-- @todo: document PgSQL upgrade once they are implemented in kea-admin --> <!-- @todo: document PgSQL upgrade once they are implemented in kea-admin -->
</section> </section>
</section> <!-- end of PostgreSQL sections --> </section> <!-- end of PostgreSQL sections -->
<section>
<title>Limitations related to the use of the SQL databases</title>
<para>
The lease expiration time is stored in the SQL database for each lease
as a timestamp value. Kea developers observed that MySQL database doesn't
accept timestamps beyond 2147483647 seconds (maximum signed 32-bit number)
from the beginning of the epoch. At the same time, some versions of PostgreSQL
do accept greater values but the value is altered when it is read back.
For this reason the lease database backends put the restriction for the
maximum timestamp to be stored in the database, which is equal to the
maximum signed 32-bit number. This effectively means that the current
Kea version can't store the leases which expiration time is later than
2147483647 seconds since the beginning of the epoch (around year 2038).
</para>
</section>
</section> <!-- End of Database sections --> </section> <!-- End of Database sections -->
</chapter> </chapter>