aboutsummaryrefslogtreecommitdiff
path: root/src/backend
diff options
context:
space:
mode:
authorAlvaro Herrera <alvherre@alvh.no-ip.org>2014-12-03 11:52:15 -0300
committerAlvaro Herrera <alvherre@alvh.no-ip.org>2014-12-03 11:52:15 -0300
commit6597ec9be6a9ed50390f73235d6654ec32a0b944 (patch)
tree1d671c9263bdfd4128cc9e0fb406ddf47f6d5f49 /src/backend
parentbc2f43eaa4cef83798692e57e9d0364f0bcce021 (diff)
downloadpostgresql-6597ec9be6a9ed50390f73235d6654ec32a0b944.tar.gz
postgresql-6597ec9be6a9ed50390f73235d6654ec32a0b944.zip
Fix typos
Diffstat (limited to 'src/backend')
-rw-r--r--src/backend/access/transam/clog.c2
-rw-r--r--src/backend/access/transam/xloginsert.c2
2 files changed, 2 insertions, 2 deletions
diff --git a/src/backend/access/transam/clog.c b/src/backend/access/transam/clog.c
index 313bd042404..cb7ef28c472 100644
--- a/src/backend/access/transam/clog.c
+++ b/src/backend/access/transam/clog.c
@@ -419,7 +419,7 @@ TransactionIdGetStatus(TransactionId xid, XLogRecPtr *lsn)
*
* Testing during the PostgreSQL 9.2 development cycle revealed that on a
* large multi-processor system, it was possible to have more CLOG page
- * requests in flight at one time than the numebr of CLOG buffers which existed
+ * requests in flight at one time than the number of CLOG buffers which existed
* at that time, which was hardcoded to 8. Further testing revealed that
* performance dropped off with more than 32 CLOG buffers, possibly because
* the linear buffer search algorithm doesn't scale well.
diff --git a/src/backend/access/transam/xloginsert.c b/src/backend/access/transam/xloginsert.c
index f1bf728c3d2..f3d610f423c 100644
--- a/src/backend/access/transam/xloginsert.c
+++ b/src/backend/access/transam/xloginsert.c
@@ -299,7 +299,7 @@ XLogRegisterBlock(uint8 block_id, RelFileNode *rnode, ForkNumber forknum,
* Add data to the WAL record that's being constructed.
*
* The data is appended to the "main chunk", available at replay with
- * XLogGetRecData().
+ * XLogRecGetData().
*/
void
XLogRegisterData(char *data, int len)