Re: [HACKERS] Replication/backup defaults - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: [HACKERS] Replication/backup defaults
Date
Msg-id CANP8+jLg1J43ReDJntXWupTyjund5EZCQmus7RrMtVPCjXXrhw@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Replication/backup defaults  (Magnus Hagander <magnus@hagander.net>)
Responses Re: [HACKERS] Replication/backup defaults  (Magnus Hagander <magnus@hagander.net>)
Re: [HACKERS] Replication/backup defaults  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-hackers
On 2 January 2017 at 09:39, Magnus Hagander <magnus@hagander.net> wrote:

> Please do submit a patch for it.

The way this is supposed to go is someone submits a patch and they
receive feedback, then act on that feedback. If I was able to get away
with deflecting all review comments with a simple "you fix it if you
don't like it" there would be considerably more patches with my name
on it accepted, but probably no further forward in real terms because
of the loose ends it creates.

In this case, simply changing the default will remove a whole class of
performance optimization that we have educated people to expect. I'm
sorry to point this out but removing that will cause many real changes
for people's systems that we will not be thanked for, even though I
understand your reasoning and wish the same goals to be achieved.

I'm willing to assist in a project to allow changing wal_level online
in this release. Please let's follow that path.

-- 
Simon Riggs                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: [HACKERS] proposal: session server side variables
Next
From: Magnus Hagander
Date:
Subject: Re: [HACKERS] Replication/backup defaults