aboutsummaryrefslogtreecommitdiff
path: root/src
diff options
context:
space:
mode:
authorStephen Frost <sfrost@snowman.net>2018-12-04 11:04:54 -0500
committerStephen Frost <sfrost@snowman.net>2018-12-04 11:04:54 -0500
commitf502fc88b3c8b4c619a4bcbb86c3225a699c1d45 (patch)
tree132dd59b8118f3d5467e1d02af501740bce59f86 /src
parentf8f6e44676ef38fee7a5bbe4f256a34ea7799ac1 (diff)
downloadpostgresql-f502fc88b3c8b4c619a4bcbb86c3225a699c1d45.tar.gz
postgresql-f502fc88b3c8b4c619a4bcbb86c3225a699c1d45.zip
Fix typo
Backends don't typically exist uncleanly, but they can certainly exit uncleanly, and it's exiting uncleanly that's being discussed here.
Diffstat (limited to 'src')
-rw-r--r--src/backend/libpq/be-secure.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/libpq/be-secure.c b/src/backend/libpq/be-secure.c
index 7cfafb59081..3620b8ce8c1 100644
--- a/src/backend/libpq/be-secure.c
+++ b/src/backend/libpq/be-secure.c
@@ -180,7 +180,7 @@ retry:
/*
* If the postmaster has died, it's not safe to continue running,
* because it is the postmaster's job to kill us if some other backend
- * exists uncleanly. Moreover, we won't run very well in this state;
+ * exits uncleanly. Moreover, we won't run very well in this state;
* helper processes like walwriter and the bgwriter will exit, so
* performance may be poor. Finally, if we don't exit, pg_ctl will be
* unable to restart the postmaster without manual intervention, so no