postgrespro.git / summary / log / commit / refs

commit    f502fc88b3c8b4c619a4bcbb86c3225a699c1d45
Author:   Stephen Frost <sfrost@snowman.net>
Date:     Tue Dec 04 16:04:54 2018 +0000

    Fix typo
    
    Backends don't typically exist uncleanly, but they can certainly exit
    uncleanly, and it's exiting uncleanly that's being discussed here.


 src/backend/libpq/be-secure.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/backend/libpq/be-secure.c b/src/backend/libpq/be-secure.c
index 7cfafb5908..3620b8ce8c 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


[parent: f8f6e44676ef]