Postgres Pro
Downloads
Home   >   mailing lists

Re: [HACKERS] [PATCH] guc-ify the formerly hard-coded MAX_SEND_SIZEto max_wal_send - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: [HACKERS] [PATCH] guc-ify the formerly hard-coded MAX_SEND_SIZEto max_wal_send
Date
Msg-id 4135ad2d-b455-5c8a-a8ec-29125a7b140e@BlueTreble.com
Whole thread Raw
In response to [HACKERS] [PATCH] guc-ify the formerly hard-coded MAX_SEND_SIZE to max_wal_send  (Jonathon Nelson <jdnelson@dyn.com>)
Responses Re: [HACKERS] [PATCH] guc-ify the formerly hard-coded MAX_SEND_SIZEto max_wal_send  (Jon Nelson <jnelson+pgsql@jamponi.net>)
List pgsql-hackers
Tree view 
On 1/5/17 12:55 PM, Jonathon Nelson wrote:
> Attached please find a patch for PostgreSQL 9.4 which changes the
> maximum amount of data that the wal sender will send at any point in
> time from the hard-coded value of 128KiB to a user-controllable value up
> to 16MiB. It has been primarily tested under 9.4 but there has been some
> testing with 9.5.

To make sure this doesn't get lost, please add it to 
https://commitfest.postgresql.org. Please verify the patch will apply 
against current HEAD and pass make check-world.
-- 
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)

pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: [HACKERS] Re: Clarifying "server starting" messaging in pg_ctlstart without --wait
Next
From: Jim Nasby
Date:
Subject: [HACKERS] Allow controlling location of tmp_install