0001-Fix-comment-for-max_cached_tuplebufs-definition.patch

application/octet-stream

Filename: 0001-Fix-comment-for-max_cached_tuplebufs-definition.patch
Type: application/octet-stream
Part: 0
Message: Fix comment for max_cached_tuplebufs definition

Patch

Same data as JSON: GET /api/v1/attachments/:id/patch the parsed metadata as JSON — format, series position, per-file stats; never the diff bytes. API reference →
Format: format-patch
Series: patch 0001
Subject: Fix comment for max_cached_tuplebufs definition
File+
src/backend/replication/logical/reorderbuffer.c 1 1
From 07ee0e4c860e0c16a41809a175166f3837988901 Mon Sep 17 00:00:00 2001
From: Kuntal Ghosh <kuntal.ghosh@enterprisedb.com>
Date: Fri, 7 Feb 2020 14:44:37 +0530
Subject: [PATCH] Fix comment for max_cached_tuplebufs definition

---
 src/backend/replication/logical/reorderbuffer.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/backend/replication/logical/reorderbuffer.c b/src/backend/replication/logical/reorderbuffer.c
index 0f607bab70..c970324b63 100644
--- a/src/backend/replication/logical/reorderbuffer.c
+++ b/src/backend/replication/logical/reorderbuffer.c
@@ -157,7 +157,7 @@ static const Size max_changes_in_memory = 4096;
  * major bottleneck, especially when spilling to disk while decoding batch
  * workloads.
  */
-static const Size max_cached_tuplebufs = 4096 * 2;	/* ~8MB */
+static const Size max_cached_tuplebufs = 4096 * 2;	/* ~64MB */
 
 /* ---------------------------------------
  * primary reorderbuffer support routines
-- 
2.17.1