postgres.git / summary / log / commit / refs

commit    170679216d225d979daf2651f2bf73bc08ffdd26
Author:   Bruce Momjian <bruce@momjian.us>
Date:     Sat Mar 14 21:36:54 2020 +0000
First released in: 9.5.22, 9.6.18, 10.13

    C comment:  correct commented bytes of max_cached_tuplebufs
    
    The comment said ~8MB, but it is actually ~64MB.
    
    Reported-by: Kuntal Ghosh
    
    Discussion: https://postgr.es/m/CAGz5QC+GGmHdnxp04B6wcLz2Zcd_HU+wCBrsPyOZP62-BJghig@mail.gmail.com
    
    Backpatch-through: 9.5-10


 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 94266505afb..165ba8fde10 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


[parent: 61d14971dade]