NotificationsYou must be signed in to change notification settings
Fork5
Star26

Commite0226a9

committed

In postgresql.conf.sample, use on/off rather than true/false.

We used to be consistent about this, but my recent patch to add arestart_after_crash GUC failed to follow the existing convention.Report and patch from Fujii Masao.

1 parent7badf1b commite0226a9Copy full SHA for e0226a9

File tree

1 file changed

-2

lines changed

src/backend/utils/misc
- postgresql.conf.sample

1 file changed

-2

lines changed

`‎src/backend/utils/misc/postgresql.conf.sample`

Lines changed: 2 additions & 2 deletions

Original file line number	Diff line number	Diff line change
`@@ -524,8 +524,8 @@`
`524`	`524`	`# ERROR HANDLING`
`525`	`525`	`#------------------------------------------------------------------------------`
`526`	`526`
`527`		`-#exit_on_error =false# terminate session on any error?`
`528`		`-#restart_after_crash =true# reinitialize after backend crash?`
	`527`	`+#exit_on_error =off# terminate session on any error?`
	`528`	`+#restart_after_crash =on# reinitialize after backend crash?`
`529`	`529`
`530`	`530`
`531`	`531`	`#------------------------------------------------------------------------------`

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!

Commite0226a9

File tree

1 file changed

1 file changed

`‎src/backend/utils/misc/postgresql.conf.sample`

0 commit comments