diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2016-08-04 16:06:14 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2016-08-04 16:06:14 -0400 |
| commit | c1d6ee879285969a93f244e08a3ff2344d2cd7ff (patch) | |
| tree | 8708c5baf1e8f670378368d4da84056fc3a154a3 /src/tutorial/funcs.source | |
| parent | 4c275117cc1bd0d25e3515aabf4a3cb8e2e7e515 (diff) | |
| download | postgresql-c1d6ee879285969a93f244e08a3ff2344d2cd7ff.tar.gz postgresql-c1d6ee879285969a93f244e08a3ff2344d2cd7ff.zip | |
Fix bogus coding in WaitForBackgroundWorkerShutdown().
Some conditions resulted in "return" directly out of a PG_TRY block,
which left the exception stack dangling, and to add insult to injury
failed to restore the state of set_latch_on_sigusr1.
This is a bug only in 9.5; in HEAD it was accidentally fixed by commit
db0f6cad4, which removed the surrounding PG_TRY block. However, I (tgl)
chose to apply the patch to HEAD as well, because the old coding was
gratuitously different from WaitForBackgroundWorkerStartup(), and there
would indeed have been no bug if it were done like that to start with.
Dmitry Ivanov
Discussion: <1637882.WfYN5gPf1A@abook>
Diffstat (limited to 'src/tutorial/funcs.source')
0 files changed, 0 insertions, 0 deletions