diff options
| author | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2020-05-22 17:39:16 -0400 |
|---|---|---|
| committer | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2020-05-22 17:39:16 -0400 |
| commit | c99cec96b8b1e067744b8a70961a3447a2293de0 (patch) | |
| tree | 542f1862ae674f6e9cebe44b2f3ecf47debdc0f0 /src/backend | |
| parent | eaae947e2b99a84c8f321fe084d87daff0f77d02 (diff) | |
| download | postgresql-c99cec96b8b1e067744b8a70961a3447a2293de0.tar.gz postgresql-c99cec96b8b1e067744b8a70961a3447a2293de0.zip | |
Fix two typos in a comment
They were introduced in 898e5e3290a7; backpatch to 12.
Diffstat (limited to 'src/backend')
| -rw-r--r-- | src/backend/partitioning/partdesc.c | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/src/backend/partitioning/partdesc.c b/src/backend/partitioning/partdesc.c index e7f23542e80..0f124a52540 100644 --- a/src/backend/partitioning/partdesc.c +++ b/src/backend/partitioning/partdesc.c @@ -150,9 +150,9 @@ RelationBuildPartitionDesc(Relation rel) * tuple or an old one where relpartbound is NULL. In that case, try * the table directly. We can't just AcceptInvalidationMessages() and * retry the system cache lookup because it's possible that a - * concurrent ATTACH PARTITION operation has removed itself to the - * ProcArray but yet added invalidation messages to the shared queue; - * InvalidateSystemCaches() would work, but seems excessive. + * concurrent ATTACH PARTITION operation has removed itself from the + * ProcArray but not yet added invalidation messages to the shared + * queue; InvalidateSystemCaches() would work, but seems excessive. * * Note that this algorithm assumes that PartitionBoundSpec we manage * to fetch is the right one -- so this is only good enough for |