Re: max_wal_senders must die

From: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: postgres hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: max_wal_senders must die
Date: 2010-10-19 11:14:30
Message-ID: 4CBD7D96.10006@kaltenbrunner.cc
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Josh Berkus wrote:
> Hackers,
>
> What purpose is served, exactly, by max_wal_senders?
>
> In order for a standby to connect, it must have a superuser login, and
> replication connections must be enabled in pg_hba.conf. How is having
> one more setting in one more file you have to enable on the master
> benefitting anyone?
>
> Under what bizarre set of circumstances would anyone have runaway
> connections from replicas to the master?
>
> Proposed that we simply remove this setting in 9.1. The real maximum
> wal senders should be whatever max_connections is.

I disagree - limiting the maximum number of replication connections is
important for my usecases.
Replication connections are significantly more heavilyweight than a
normal connection and right now I for example simply use this setting to
prevent stupid mistakes (especially in virtualized^cloudstyle environments).

What we really should look into is using a less privileged role - or
dedicated replication role - and use the existing per role connection
limit feature. That feature is unlimited by default, people can change
it like for every role and we can git rid of that guc.

Stefan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2010-10-19 11:18:07 Re: max_wal_senders must die
Previous Message Dimitri Fontaine 2010-10-19 09:27:00 Re: Extensions, this time with a patch