mirror of
https://github.com/supabase/supabase.git
synced 2026-10-16 22:59:11 +03:00
fix sentence casing
This commit is contained in:
2 files changed
+4
-4
No files matched your search
@@ -40,7 +40,7 @@ To set up sharding and partitioning, you can partition your tables and store eac
|
||||
SERVER shard2 OPTIONS (table_name 'sales_2000_02');
|
||||
```
|
||||
|
||||
## Moving partitions Between Shards
|
||||
## Moving partitions between shards
|
||||
|
||||
To move a partition from one shard to another, you can use the following steps:
|
||||
|
||||
@@ -79,7 +79,7 @@ FROM sales
|
||||
WHERE order_date >= '2000-01-01' AND order_date < '2000-03-01';
|
||||
```
|
||||
|
||||
### Querying specific Partitions
|
||||
### Querying specific partitions
|
||||
|
||||
If you only need to retrieve data from a specific partition, you can directly query that partition.
|
||||
|
||||
|
||||
@@ -65,7 +65,7 @@ For each project, you will need to:
|
||||
|
||||
The steps outlined below are for `shard01` and would be repeated on each shard, replacing the shard names.
|
||||
|
||||
### Example - shard01
|
||||
### Example
|
||||
|
||||
1. **Install the `postgres_fdw` extension**:
|
||||
|
||||
@@ -115,7 +115,7 @@ The steps outlined below are for `shard01` and would be repeated on each shard,
|
||||
|
||||
By following these steps, you can distribute your data across multiple Postgres databases and query them as if they were a single database, improving performance and scalability.
|
||||
|
||||
## Use cases for sharding
|
||||
## Use cases
|
||||
|
||||
Sharding can be particularly useful in the following scenarios:
|
||||
|
||||
|
||||
Reference in new issue
Block a user