NotificationsYou must be signed in to change notification settings
Fork6
Star31

Commit99e3298

committed

Remove pg_dump/parallel.c's useless "aborting" flag.

This was effectively dead code, since the places that tested it could notbe reached after we entered the on-exit-cleanup routine that would set it.It seems to have been a leftover from a design in which error abort wouldtry to send fresh commands to the workers --- a design which could neverhave worked reliably, of course. Since the flag is not cross-platform, itcomplicates reasoning about the code's behavior, which we could do without.Although this is effectively just cosmetic, back-patch anyway, becausethere are some actual bugs in the vicinity of this behavior.Discussion: <15583.1464462418@sss.pgh.pa.us>

1 parent24c1f64 commit99e3298Copy full SHA for 99e3298

File tree

1 file changed

-28

lines changed

src/bin/pg_dump
- parallel.c

1 file changed

-28

lines changed

`‎src/bin/pg_dump/parallel.c`

Lines changed: 6 additions & 28 deletions

Original file line number	Diff line number	Diff line change
`@@ -95,11 +95,7 @@ static intpiperead(int s, char *buf, int len);`
`95`	`95`
`96`	`96`	`#else/* !WIN32 */`
`97`	`97`
`98`		`-/*`
`99`		`- * Variables for handling signals. aborting is only ever used in the master,`
`100`		`- * the workers just need wantAbort.`
`101`		`- */`
`102`		`-staticboolaborting= false;`
	`98`	`+/* Signal handler flag */`
`103`	`99`	`staticvolatilesig_atomic_twantAbort=0;`
`104`	`100`
`105`	`101`	`/* Non-Windows implementation of pipe access */`
`@@ -301,14 +297,6 @@ archive_close_connection(int code, void *arg)`
`301`	`297`	`if (si->AHX)`
`302`	`298`	`DisconnectDatabase(si->AHX);`
`303`	`299`
`304`		`-#ifndefWIN32`
`305`		`-`
`306`		`-/*`
`307`		`- * Setting aborting to true shuts off error/warning messages that`
`308`		`- * are no longer useful once we start killing workers.`
`309`		`- */`
`310`		`-aborting= true;`
`311`		`-#endif`
`312`	`300`	`ShutdownWorkersHard(si->pstate);`
`313`	`301`	`}`
`314`	`302`	`else`
`@@ -1180,11 +1168,9 @@ select_loop(int maxFd, fd_set *workerset)`
`1180`	`1168`	`/*`
`1181`	`1169`	`* If we Ctrl-C the master process, it's likely that we interrupt`
`1182`	`1170`	`* select() here. The signal handler will set wantAbort == true and`
`1183`		`- * the shutdown journey starts from here. Note that we'll come back`
`1184`		`- * here later when we tell all workers to terminate and read their`
`1185`		`- * responses. But then we have aborting set to true.`
	`1171`	`+ * the shutdown journey starts from here.`
`1186`	`1172`	`*/`
`1187`		`-if (wantAbort&& !aborting)`
	`1173`	`+if (wantAbort)`
`1188`	`1174`	`exit_horribly(modulename,"terminated by user\n");`
`1189`	`1175`
`1190`	`1176`	`if (i<0&&errno==EINTR)`
`@@ -1281,17 +1267,9 @@ sendMessageToWorker(ParallelState pstate, int worker, const char str)`
`1281`	`1267`
`1282`	`1268`	`if (pipewrite(pstate->parallelSlot[worker].pipeWrite,str,len)!=len)`
`1283`	`1269`	`{`
`1284`		`-/*`
`1285`		`- * If we're already aborting anyway, don't care if we succeed or not.`
`1286`		`- * The child might have gone already. (XXX but if we're aborting`
`1287`		`- * already, why are we here at all?)`
`1288`		`- */`
`1289`		`-#ifndefWIN32`
`1290`		`-if (!aborting)`
`1291`		`-#endif`
`1292`		`-exit_horribly(modulename,`
`1293`		`-"could not write to the communication channel: %s\n",`
`1294`		`-strerror(errno));`
	`1270`	`+exit_horribly(modulename,`
	`1271`	`+"could not write to the communication channel: %s\n",`
	`1272`	`+strerror(errno));`
`1295`	`1273`	`}`
`1296`	`1274`	`}`
`1297`	`1275`

0 commit comments

Comments

(0)

Movatterモバイル変換

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Commit99e3298

File tree

1 file changed

1 file changed

`‎src/bin/pg_dump/parallel.c`

0 commit comments