aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/heap/heapam.c
diff options
context:
space:
mode:
authorHeikki Linnakangas <heikki.linnakangas@iki.fi>2011-11-10 12:09:33 +0200
committerHeikki Linnakangas <heikki.linnakangas@iki.fi>2011-11-10 12:21:43 +0200
commit2e02280726f5ca7a8e3c76e1491eaf5ab00fc8f4 (patch)
tree663f401239c65bd38788b25ba87b7fba9d4d9902 /src/backend/access/heap/heapam.c
parent6f2efcd557bb3309e70751daf1fb7c74bbaa4061 (diff)
downloadpostgresql-2e02280726f5ca7a8e3c76e1491eaf5ab00fc8f4.tar.gz
postgresql-2e02280726f5ca7a8e3c76e1491eaf5ab00fc8f4.zip
Fix another bug in the redo of COPY batches.
I got alignment wrong in the redo routine. Spotted by redoing the log genereated by copy regression test.
Diffstat (limited to 'src/backend/access/heap/heapam.c')
-rw-r--r--src/backend/access/heap/heapam.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/access/heap/heapam.c b/src/backend/access/heap/heapam.c
index 9b49302c789..630c3ab26c0 100644
--- a/src/backend/access/heap/heapam.c
+++ b/src/backend/access/heap/heapam.c
@@ -5111,7 +5111,7 @@ heap_xlog_multi_insert(XLogRecPtr lsn, XLogRecord *record)
elog(PANIC, "heap_multi_insert_redo: invalid max offset number");
xlhdr = (xl_multi_insert_tuple *) SHORTALIGN(recdata);
- recdata += SizeOfMultiInsertTuple;
+ recdata = ((char *) xlhdr) + SizeOfMultiInsertTuple;
newlen = xlhdr->datalen;
Assert(newlen <= MaxHeapTupleSize);