NotificationsYou must be signed in to change notification settings
Fork6
Star31

Commit0c32818

committed

Be more rigorous about local variables in PostgresMain().

Since PostgresMain calls sigsetjmp, any local variables that are notmarked "volatile" have a risk of unspecified behavior. In practicethis means that when control returns via longjmp, such variables mightget reset to their values as of the time of sigsetjmp, depending onwhether the compiler chose to put them in registers or on the stack.We were careful about this for "send_ready_for_query", but not theother local variables.In the case of the timeout_enabled flags, resetting them totheir initial "false" states is actually good, since we do"disable_all_timeouts()" in the longjmp cleanup code path. If thatdoes not happen, we risk uselessly calling "disable_timeout()" later,which is harmless but a little bit expensive. Let's explicitly resetthese flags so that the behavior is correct and platform-independent.(This change means that we really don't need the new "volatile"markings after all, but let's install them anyway since any changein this logic could re-introduce a problem.)There is no issue for "firstchar" and "input_message" because thoseare explicitly reinitialized each time through the query processingloop. To make that clearer, move them to be declared inside the loop.That leaves us with all the function-lifespan locals except thesigjmp_buf itself marked as volatile, which seems like a good policyto have going forward.Because of the possibility of extra disable_timeout() calls, thisseems worth back-patching.Sergey Shinderuk and Tom LaneDiscussion:https://postgr.es/m/2eda015b-7dff-47fd-d5e2-f1a9899b90a6@postgrespro.ru

1 parent02021f1 commit0c32818Copy full SHA for 0c32818

File tree

1 file changed

-5

lines changed

src/backend/tcop
- postgres.c

1 file changed

-5

lines changed

`‎src/backend/tcop/postgres.c`

Lines changed: 9 additions & 5 deletions

Original file line number	Diff line number	Diff line change
`@@ -3753,11 +3753,11 @@ PostgresMain(int argc, char *argv[],`
`3753`	`3753`	`constchar*dbname,`
`3754`	`3754`	`constchar*username)`
`3755`	`3755`	`{`
`3756`		`-intfirstchar;`
`3757`		`-StringInfoDatainput_message;`
`3758`	`3756`	`sigjmp_buflocal_sigjmp_buf;`
	`3757`	`+`
	`3758`	`+/* these must be volatile to ensure state is preserved across longjmp: */`
`3759`	`3759`	`volatileboolsend_ready_for_query= true;`
`3760`		`-booldisable_idle_in_transaction_timeout= false;`
	`3760`	`+volatilebooldisable_idle_in_transaction_timeout= false;`
`3761`	`3761`
`3762`	`3762`	`/* Initialize startup process environment if necessary. */`
`3763`	`3763`	`if (!IsUnderPostmaster)`
`@@ -4042,9 +4042,10 @@ PostgresMain(int argc, char *argv[],`
`4042`	`4042`	`* query cancels from being misreported as timeouts in case we're`
`4043`	`4043`	`* forgetting a timeout cancel.`
`4044`	`4044`	`*/`
`4045`		`-disable_all_timeouts(false);`
`4046`		`-QueryCancelPending= false;/* second to avoid race condition */`
	`4045`	`+disable_all_timeouts(false);/* do first to avoid race condition */`
	`4046`	`+QueryCancelPending= false;`
`4047`	`4047`	`stmt_timeout_active= false;`
	`4048`	`+disable_idle_in_transaction_timeout= false;`
`4048`	`4049`
`4049`	`4050`	`/* Not reading from the client anymore. */`
`4050`	`4051`	`DoingCommandRead= false;`
`@@ -4133,6 +4134,9 @@ PostgresMain(int argc, char *argv[],`
`4133`	`4134`
`4134`	`4135`	`for (;;)`
`4135`	`4136`	`{`
	`4137`	`+intfirstchar;`
	`4138`	`+StringInfoDatainput_message;`
	`4139`	`+`
`4136`	`4140`	`/*`
`4137`	`4141`	`* At top of loop, reset extended-query-message flag, so that any`
`4138`	`4142`	`* errors encountered in "idle" state don't provoke skip.`

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!

Commit0c32818

File tree

1 file changed

1 file changed

`‎src/backend/tcop/postgres.c`

0 commit comments