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 | 8fdde45e32e486903d6866a4b0a761f418463493 (patch) | |
| tree | 39acfb915e32ecec398b8fa2ae335e645109acd3 /src/backend | |
| parent | a87209ce7e1270b3a48e107c981a7035196d662b (diff) | |
| download | postgresql-8fdde45e32e486903d6866a4b0a761f418463493.tar.gz postgresql-8fdde45e32e486903d6866a4b0a761f418463493.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 b207b765f2a..ae193681b96 100644 --- a/src/backend/partitioning/partdesc.c +++ b/src/backend/partitioning/partdesc.c @@ -116,9 +116,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 |