Merge branch 'latest' into fix/pr-comment-url

api/add_data_node.md

@@ -101,11 +101,10 @@ TimescaleDB extension on the data node unless it is already installed.
 
 ### Sample usage
 
-Let's assume that you have an existing hypertable `conditions` and
-want to use `time` as the time partitioning column and `location` as
-the space partitioning column. You also want to distribute the chunks
-of the hypertable on two data nodes `dn1.example.com` and
-`dn2.example.com`:
+If you have an existing hypertable `conditions` and want to use `time`
+as the time partitioning column and `location` as the space partitioning
+column. You also want to distribute the chunks of the hypertable on two
+data nodes `dn1.example.com` and `dn2.example.com`:
 
 ```sql
 SELECT add_data_node('dn1', host => 'dn1.example.com');

api/create_hypertable.md

@@ -147,19 +147,6 @@ SELECT create_hypertable('conditions', 'time', chunk_time_interval => 8640000000
 SELECT create_hypertable('conditions', 'time', chunk_time_interval => INTERVAL '1 day');
 ```
 
-Convert table `conditions` to hypertable with time partitioning on `time` and
-space partitioning (4 partitions) on `location`:
-
-```sql
-SELECT create_hypertable('conditions', 'time', 'location', 4);
-```
-
-The same as above, but using a custom partitioning function:
-
-```sql
-SELECT create_hypertable('conditions', 'time', 'location', 4, partitioning_func => 'location_hash');
-```
-
 Convert table `conditions` to hypertable. Do not raise a warning
 if `conditions` is already a hypertable:
 

self-hosted/distributed-hypertables/create-distributed-hypertables.md

@@ -35,8 +35,7 @@ hypertable. To set up multi-node, see the
 
 1.  Convert the table to a distributed hypertable. Specify the name of the table
     you want to convert, the column that holds its time values, and a
-    space-partitioning parameter. For more information about space partitions,
-    see the [space-partitioning section][space-partitions].
+    space-partitioning parameter.
 
      ```sql
      SELECT create_distributed_hypertable('conditions', 'time', 'location');
@@ -46,4 +45,3 @@ hypertable. To set up multi-node, see the
 
 [multi-node]: /self-hosted/:currentVersion:/multinode-timescaledb/
 [postgres-createtable]: https://www.postgresql.org/docs/current/sql-createtable.html
-[space-partitions]: /use-timescale/:currentVersion:/hypertables/about-hypertables#space-partitions-for-distributed-hypertables

use-timescale/hypertables/about-hypertables.md

@@ -73,24 +73,6 @@ For a detailed analysis of how to optimize your chunk sizes, see the
 to view and set your chunk time intervals, see the section on
 [changing hypertable chunk intervals][change-chunk-intervals].
 
-### Space partitioning
-
-Space partitioning is optional. It is not usually recommended for regular
-hypertables.
-
-A good alternative way to increase input/output performance on single
-hypertables is to use RAID (redundant array of inexpensive disks). RAID
-virtualizes multiple physical disks into a single logical disk. You can then use
-this single logical disk to store your hypertable, without any space
-partitioning.
-
-Space partitioning is useful if you have multiple physical disks, each
-corresponding to a separate tablespace. Each disk can then store some of the
-space partitions. If you partition by space without this setup, you increase
-query planning complexity without increasing I/O performance. For more
-information, see the
-[distributed hypertables][about-distributed-hypertables] section.
-
 ## Hypertable indexes
 
 By default, indexes are automatically created when you create a hypertable. You