From d368b8654f99fea745f87384d91db765ae7631ab Mon Sep 17 00:00:00 2001 From: "Eric.wangpeng" Date: Fri, 28 Aug 2020 13:23:13 +0800 Subject: [PATCH] update content/en/docs/Developerguide/creating-dropping-an-mot-table.md. Update MOT limitations. --- content/en/docs/Developerguide/creating-dropping-an-mot-table.md | 1 + 1 file changed, 1 insertion(+) diff --git a/content/en/docs/Developerguide/creating-dropping-an-mot-table.md b/content/en/docs/Developerguide/creating-dropping-an-mot-table.md index 3aa869a0f..5b468b8bf 100644 --- a/content/en/docs/Developerguide/creating-dropping-an-mot-table.md +++ b/content/en/docs/Developerguide/creating-dropping-an-mot-table.md @@ -11,6 +11,7 @@ Creating a Memory Optimized Table \(MOT\) is very simple. Only the create and dr - Always use the FOREIGN keyword to refer to MOT tables. - The \[server mot\_server\] part is optional when creating an MOT table because MOT is an integrated engine, not a separate server. - The above is an extremely simple example creating a table named **test** with a single integer column named **x**. In the next section \(**Creating an Index**\) a more realistic example is provided. +- MOT tables cannot be created if incremental checkpoint is enabled in postgresql.conf. - To drop an MOT table named test – ``` -- Gitee