Commitf502fc8

committed

Fix typo

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

1 parentf8f6e44 commitf502fc8Copy full SHA for f502fc8

File tree

-1

lines changed

-1

lines changed

Lines changed: 1 addition & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -180,7 +180,7 @@ secure_read(Port port, void ptr, size_t len)`
`180`	`180`	`/*`
`181`	`181`	`* If the postmaster has died, it's not safe to continue running,`
`182`	`182`	`* because it is the postmaster's job to kill us if some other backend`
`183`		`- *exists uncleanly. Moreover, we won't run very well in this state;`
	`183`	`+ *exits uncleanly. Moreover, we won't run very well in this state;`
`184`	`184`	`* helper processes like walwriter and the bgwriter will exit, so`
`185`	`185`	`* performance may be poor. Finally, if we don't exit, pg_ctl will be`
`186`	`186`	`* unable to restart the postmaster without manual intervention, so no`

Comments

(0)