Re: max_wal_senders must die - Mailing list pgsql-hackers

From Joshua D. Drake
Subject Re: max_wal_senders must die
Date
Msg-id 1288208412.8120.104.camel@jd-desktop
Whole thread Raw
In response to Re: max_wal_senders must die  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, 2010-10-27 at 15:33 -0400, Tom Lane wrote:
> Josh Berkus <josh@agliodbs.com> writes:
> >>> Josh has completely failed to make a case that
> >>> that should be the default.
> >> 
> >> Agreed.
> 
> > In what way have a failed to make a case?
> 
> You're assuming that we should set up the default behavior to support
> replication and penalize those who aren't using it. 
>  Considering that
> we haven't even *had* replication until now, it seems a pretty safe
> bet that the majority of our users aren't using it and won't appreciate
> that default.  We routinely expend large amounts of effort to avoid
> cross-version performance regressions, and I don't see that this one
> is acceptable when others aren't.
> 
> I entirely agree that it ought to be easier to set up replication.
> But there's a difference between having a big red EASY button for people
> to push, and pushing it for them.

Replication is an option, not a requirement. So +1 on Tom's argument
here.

> 
>             regards, tom lane
> 

-- 
PostgreSQL.org Major Contributor
Command Prompt, Inc: http://www.commandprompt.com/ - 509.416.6579
Consulting, Training, Support, Custom Development, Engineering
http://twitter.com/cmdpromptinc | http://identi.ca/commandprompt



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Simplifying replication
Next
From: Fujii Masao
Date:
Subject: Re: xlog.c: WALInsertLock vs. WALWriteLock