Skip to content

Commit cee3b74

Browse files
committed
Acrolinx
1 parent 036f88a commit cee3b74

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/postgresql/hyperscale/concepts-performance-tuning.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -51,7 +51,7 @@ meaning of the query.
5151

5252
In some workloads, it's easy. Transactional/operational workloads like
5353
multi-tenant SaaS apps or the Internet of Things distribute tables by tenant or
54-
device. Queries are usually scoped to a tenant- or device-ID.
54+
device. Queries are scoped to a tenant- or device-ID.
5555

5656
For instance, in our [multi-tenant
5757
tutorial](tutorial-design-database-multi-tenant.md#use-psql-utility-to-create-a-schema)
@@ -129,12 +129,12 @@ SELECT *
129129

130130
In general, when joining distributed tables, try to include the distribution
131131
column in the join conditions. However, when joining between a distributed and
132-
reference table you don't need to do this, because reference table contents are
132+
reference table it's not required, because reference table contents are
133133
replicated across all worker nodes.
134134

135-
If it seems inconvenient to add the additional filters to all your queries,
136-
keep in mind there are helper libraries for several popular application
137-
frameworks that make it easier. Here are instructions:
135+
If it seems inconvenient to add the extra filters to all your queries, keep in
136+
mind there are helper libraries for several popular application frameworks that
137+
make it easier. Here are instructions:
138138

139139
* [Ruby on Rails](https://docs.citusdata.com/en/stable/develop/migration_mt_ror.html),
140140
* [Django](https://docs.citusdata.com/en/stable/develop/migration_mt_django.html),

0 commit comments

Comments
 (0)