forked frompostgres/postgres
- Notifications
You must be signed in to change notification settings - Fork6
Commitd368a30
committed
pg_receivexlog - Exit on failure to parse
In streamutil.c:GetConnection(), upgrade failure to parse theconnection string to an exit(1) instead of simply returning NULL.Most callers already immediately exited, but pg_receivexlog wouldloop on this case, continually trying to re-parse the connectionstring (which can't be changed after pg_receivexlog has started).GetConnection() was already expected to exit(1) in some cases(eg: failure to allocate memory or if unable to determine theinteger_datetimes flag), so this change shouldn't surprise anyone.Began looking at this due to the Coverity scanner complaining thatwe were leaking err_msg in this case- no longer an issue since wejust exit(1) immediately.1 parent234e4cf commitd368a30
1 file changed
+1
-1
lines changedLines changed: 1 addition & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
57 | 57 | | |
58 | 58 | | |
59 | 59 | | |
60 | | - | |
| 60 | + | |
61 | 61 | | |
62 | 62 | | |
63 | 63 | | |
| |||
0 commit comments
Comments
(0)