Commit92fc0db

committed

Additional thoughts on WALSender cpu reduction. Use long type

and alter a comment to reduce confusion.

1 parente6867ee commit92fc0dbCopy full SHA for 92fc0db

File tree

-3

lines changed

-3

lines changed

Lines changed: 3 additions & 3 deletions

Original file line number	Diff line number	Diff line change
`@@ -30,7 +30,7 @@`
`30`	`30`	`*`
`31`	`31`	`*`
`32`	`32`	`* IDENTIFICATION`
`33`		`- * $PostgreSQL: pgsql/src/backend/replication/walsender.c,v 1.11 2010/03/2420:11:12 sriggs Exp $`
	`33`	`+ * $PostgreSQL: pgsql/src/backend/replication/walsender.c,v 1.12 2010/03/2421:41:57 sriggs Exp $`
`34`	`34`	`*`
`35`	`35`	`*-------------------------------------------------------------------------`
`36`	`36`	`*/`
`@@ -353,7 +353,7 @@ WalSndLoop(void)`
`353`	`353`	`/* Loop forever */`
`354`	`354`	`for (;;)`
`355`	`355`	`{`
`356`		`-intremain;/* remaining time (ms) */`
	`356`	`+longremain;/* remaining time (us) */`
`357`	`357`
`358`	`358`	`/*`
`359`	`359`	`* Emergency bailout if postmaster has died. This is to avoid the`
`@@ -393,7 +393,7 @@ WalSndLoop(void)`
`393`	`393`	`*`
`394`	`394`	`* On some platforms, signals won't interrupt the sleep. To ensure we`
`395`	`395`	`* respond reasonably promptly when someone signals us, break down the`
`396`		`- * sleep into NAPTIME_PER_CYCLE(ms)increments, and check for`
	`396`	`+ * sleep into NAPTIME_PER_CYCLE increments, and check for`
`397`	`397`	`* interrupts after each nap.`
`398`	`398`	`*/`
`399`	`399`	`remain=WalSndDelay*1000L;`

Comments

(0)