From d7850db40c8491d1f023dd5f532eee9ee1e8b80a Mon Sep 17 00:00:00 2001 From: Justin de Guzman Date: Mon, 12 Feb 2024 09:54:38 -0800 Subject: [PATCH] [Docs] Remove incorrect statement about Memory table engine --- docs/en/engines/table-engines/special/memory.md | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/en/engines/table-engines/special/memory.md b/docs/en/engines/table-engines/special/memory.md index 54547b1bc69..0d552a69804 100644 --- a/docs/en/engines/table-engines/special/memory.md +++ b/docs/en/engines/table-engines/special/memory.md @@ -10,7 +10,6 @@ sidebar_label: Memory When using the Memory table engine on ClickHouse Cloud, data is not replicated across all nodes (by design). To guarantee that all queries are routed to the same node and that the Memory table engine works as expected, you can do one of the following: - Execute all operations in the same session - Use a client that uses TCP or the native interface (which enables support for sticky connections) such as [clickhouse-client](/en/interfaces/cli) -- Submit and execute all queries at once using a multi-statement query (required with clients using the HTTP interface such as [clickhouse-connect](/en/integrations/python)) ::: The Memory engine stores data in RAM, in uncompressed form. Data is stored in exactly the same form as it is received when read. In other words, reading from this table is completely free.