Re: [PATCH] guc-ify the formerly hard-coded MAX_SEND_SIZE to max_wal_send

From: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
To: Jonathon Nelson <jdnelson(at)dyn(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCH] guc-ify the formerly hard-coded MAX_SEND_SIZE to max_wal_send
Date: 2017-01-08 01:48:26
Message-ID: 4135ad2d-b455-5c8a-a8ec-29125a7b140e@BlueTreble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim Nasby 2017-01-08 01:52:13 Allow controlling location of tmp_install
Previous Message Jim Nasby 2017-01-08 01:48:06 Re: Re: Clarifying "server starting" messaging in pg_ctl start without --wait