<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[How large can the data field be for any of the FusionAuth resources?]]></title><description><![CDATA[<p dir="auto">Hi, how large can the data field be for any of the FusionAuth resources (user, registration, etc).</p>
]]></description><link>https://fusionauth.io/community/forum/topic/89/how-large-can-the-data-field-be-for-any-of-the-fusionauth-resources</link><generator>RSS for Node</generator><lastBuildDate>Sun, 12 Jul 2026 12:24:00 GMT</lastBuildDate><atom:link href="https://fusionauth.io/community/forum/topic/89.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 15 May 2020 20:49:13 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to How large can the data field be for any of the FusionAuth resources? on Fri, 15 May 2020 20:49:57 GMT]]></title><description><![CDATA[<p dir="auto">If you're using PostgreSQL the size is essentially unlimited. With MySQL it is 16 MB.</p>
<p dir="auto">There are few exceptions to this rule where we may be using a 64 KB column if you're on MySQL.</p>
<p dir="auto">I wouldn't recommend storing that much data however. If you're using Elasticsearch, the custom data on the User will be indexed, and Elasticsearch will eventually hit a limit as well.</p>
]]></description><link>https://fusionauth.io/community/forum/post/191</link><guid isPermaLink="true">https://fusionauth.io/community/forum/post/191</guid><dc:creator><![CDATA[dan]]></dc:creator><pubDate>Fri, 15 May 2020 20:49:57 GMT</pubDate></item></channel></rss>