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

2017-01-09 Thread Jonathon Nelson
On Sun, Jan 8, 2017 at 11:36 AM, Greg Stark wrote: > On 8 January 2017 at 17:26, Greg Stark wrote: > > On 5 January 2017 at 19:01, Andres Freund wrote: > >> That's a bit odd - shouldn't the OS network stack take care of this in > >> both cases? I mean either is too big for TCP packets (includi

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

2017-01-06 Thread Jonathon Nelson
On Fri, Jan 6, 2017 at 8:52 AM, Kevin Grittner wrote: > On Thu, Jan 5, 2017 at 7:32 PM, Jonathon Nelson wrote: > > On Thu, Jan 5, 2017 at 1:01 PM, Andres Freund > wrote: > >> On 2017-01-05 12:55:44 -0600, Jonathon Nelson wrote: > > >>> In our lab environm

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

2017-01-05 Thread Jonathon Nelson
On Thu, Jan 5, 2017 at 1:01 PM, Andres Freund wrote: > Hi, > > On 2017-01-05 12:55:44 -0600, 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 >

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

2017-01-05 Thread Jonathon Nelson
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.