diff options
| author | Amit Kapila | 2019-05-26 12:58:18 +0000 |
|---|---|---|
| committer | Amit Kapila | 2019-05-26 12:58:18 +0000 |
| commit | 9679345f3c5ec071f63db358581e28f06c8744a7 (patch) | |
| tree | 12365b3337578d66f41a58d0e2c2966d9eb3acac /contrib/postgres_fdw/postgres_fdw.c | |
| parent | 41205719d34969018f708baa70d9d06dae0c0d08 (diff) | |
Fix typos.
Reported-by: Alexander Lakhin
Author: Alexander Lakhin
Reviewed-by: Amit Kapila and Tom Lane
Discussion: https://postgr.es/m/[email protected]
Diffstat (limited to 'contrib/postgres_fdw/postgres_fdw.c')
| -rw-r--r-- | contrib/postgres_fdw/postgres_fdw.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/contrib/postgres_fdw/postgres_fdw.c b/contrib/postgres_fdw/postgres_fdw.c index 02c81ce7a95..1b09aa5a017 100644 --- a/contrib/postgres_fdw/postgres_fdw.c +++ b/contrib/postgres_fdw/postgres_fdw.c @@ -3064,7 +3064,7 @@ estimate_path_cost_size(PlannerInfo *root, total_cost += cpu_tuple_cost * retrieved_rows; /* - * If we have LIMIT, we should perfer performing the restriction remotely + * If we have LIMIT, we should prefer performing the restriction remotely * rather than locally, as the former avoids extra row fetches from the * remote that the latter might cause. But since the core code doesn't * account for such fetches when estimating the costs of the local |