Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 3E469633E65; Tue, 20 Apr 2010 11:39:37 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 74699-01-8; Tue, 20 Apr 2010 14:39:26 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-iw0-f187.google.com (mail-iw0-f187.google.com [209.85.223.187]) by mail.postgresql.org (Postfix) with ESMTP id AF637634885; Tue, 20 Apr 2010 10:42:52 -0300 (ADT) Received: by iwn17 with SMTP id 17so677721iwn.19 for ; Tue, 20 Apr 2010 06:42:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type; bh=W50TEU6144SI2fNvq3PQcW6B07dkUh0skC/WooMLXtw=; b=U90Nb7TYvh6geQPCuXBh0D5LNtNaAZolyYhmTa9SbUYwXKQSESulMmMbzApC+SeVXv n5AQrro3SxOgP/1Poi5sA33/s1lW97bStnz5R+X/VmmPh5yH5E43Zg+TH8jhTVejGGED V4zWtcUS7NjegN/1QMgQcBBUxVAMYdkOe6b5k= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=YIeLTTr+xpgapvEtz3djYHahFccpyxAaNVVdBIGFKvnKR9PY0VnmyWrODN3U0+bXwp 6byXf+8Y3f6oUYg7Kz7is55Mh3gNaXRqxgA0yL6fWLgmk7XCN4Q8CdqiQcSDknSKJWmQ 2VrSRb3ksEnpUcanbvpfkAbjU/AcZxI4A/gJg= MIME-Version: 1.0 Received: by 10.231.38.194 with HTTP; Tue, 20 Apr 2010 06:42:51 -0700 (PDT) In-Reply-To: <25868.1271770805@sss.pgh.pa.us> References: <3f0b79eb1003300152g5327eb47w8f9aecae6002b215@mail.gmail.com> <19262.1270142946@sss.pgh.pa.us> <4BB4952D0200002500030333@gw.wicourts.gov> <4BB4DBEF.3010301@agliodbs.com> <25868.1271770805@sss.pgh.pa.us> Date: Tue, 20 Apr 2010 09:42:51 -0400 Received: by 10.231.150.12 with SMTP id w12mr1048732ibv.37.1271770971864; Tue, 20 Apr 2010 06:42:51 -0700 (PDT) Message-ID: Subject: Re: [HACKERS] Streaming replication document improvements From: Robert Haas To: Tom Lane Cc: Fujii Masao , Josh Berkus , Kevin Grittner , Heikki Linnakangas , pgsql-docs@postgresql.org, PostgreSQL-development Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=2.42 tagged_above=-10 required=5 tests=BAYES_00=-1.9, FREEMAIL_FROM=0.001, FS_REPLICA=3.599, SARE_SPEC_REPLICA=0.72 X-Spam-Level: ** X-Archive-Number: 201004/66 X-Sequence-Number: 5465 On Tue, Apr 20, 2010 at 9:40 AM, Tom Lane wrote: > Robert Haas writes: >> If replication connections can use up superuser_reserved_connections >> slots, then it's very possible that this safety valve will fail >> completely. > > Only if replication can use up *all* the superuser_reserved_connections > slots. Sure. In many cases someone will have 3 superuser_reserved_connections and only 1 wal_sender, so it won't be an issue. However, I still think we oughta make this (apparently one-line) fix so that people will have the number of emergency superuser connections that they expect to have, rather than some smaller number that might be 0 if they have a number of SR slaves. ...Robert