Use correctly-sized buffer when zero-filling a WAL file.
authorHeikki Linnakangas <[email protected]>
Wed, 16 Apr 2014 07:21:09 +0000 (10:21 +0300)
committerHeikki Linnakangas <[email protected]>
Wed, 16 Apr 2014 07:27:09 +0000 (10:27 +0300)
I mixed up BLCKSZ and XLOG_BLCKSZ when I changed the way the buffer is
allocated a couple of weeks ago. With the default settings, they are both
8k, but they can be changed at compile-time.

src/backend/access/transam/xlog.c

index 8d404e726858206b34850e8a5c6deaf0bb8408a9..059c19255f6f80bcffa8fb981b95e2e7a6199796 100644 (file)
@@ -2289,7 +2289,7 @@ XLogFileInit(uint32 log, uint32 seg,
 {
    char        path[MAXPGPATH];
    char        tmppath[MAXPGPATH];
-   char        zbuffer_raw[BLCKSZ + MAXIMUM_ALIGNOF];
+   char        zbuffer_raw[XLOG_BLCKSZ + MAXIMUM_ALIGNOF];
    char       *zbuffer;
    uint32      installed_log;
    uint32      installed_seg;
@@ -2351,7 +2351,7 @@ XLogFileInit(uint32 log, uint32 seg,
     * cycles transferring data to the kernel.
     */
    zbuffer = (char *) MAXALIGN(zbuffer_raw);
-   memset(zbuffer, 0, BLCKSZ);
+   memset(zbuffer, 0, XLOG_BLCKSZ);
    for (nbytes = 0; nbytes < XLogSegSize; nbytes += XLOG_BLCKSZ)
    {
        errno = 0;