Received: from maia.hub.org (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 8A5AB632872; Wed, 31 Mar 2010 23:00:30 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 23106-05; Thu, 1 Apr 2010 02:00:10 +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-fx0-f222.google.com (mail-fx0-f222.google.com [209.85.220.222]) by mail.postgresql.org (Postfix) with ESMTP id 1D06B63357D; Wed, 31 Mar 2010 23:00:18 -0300 (ADT) Received: by fxm22 with SMTP id 22so584138fxm.34 for ; Wed, 31 Mar 2010 19:00:16 -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 :content-transfer-encoding; bh=ypgurZGNwYrh11U8WVGIkmsQLUrp+Xtoo21ow49UBK0=; b=MGORt5NHWlGogWATwuKSRA9u+7zyyXa5NoH+KxwGs4vv6SsSBl+qz6Zj+aFb8NJaKq 58YIqSYyy9FvQQ+xR1dXZBl1IDOVM4/yuS2jC7qPBO330r5UbVgiACxXOGU5LnhBk/m3 u0dz1S+ElABNoO+/vkN7cvI0sL//g7opBwsiU= 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:content-transfer-encoding; b=wHLloFy3l0CsK8Wf14te2UmK/LQnAgGeglDAqpe9+xR1wN45KWeqJyM3vYqt8kL5Fa Z0oZgycHg35vgVPh7UbiRM/KRZas9aISfeKjKGCgqPS05BCplLboUInZcNGaMANCklQz e8ZMR4357DWvJlYEWh9rXaQnrw1oXI9MVgiZ8= MIME-Version: 1.0 Received: by 10.239.161.83 with HTTP; Wed, 31 Mar 2010 19:00:16 -0700 (PDT) In-Reply-To: References: <3f0b79eb1003300152g5327eb47w8f9aecae6002b215@mail.gmail.com> <4BB3B2ED.5080606@enterprisedb.com> Date: Wed, 31 Mar 2010 22:00:16 -0400 Received: by 10.239.190.145 with SMTP id x17mr729334hbh.201.1270087216706; Wed, 31 Mar 2010 19:00:16 -0700 (PDT) Message-ID: Subject: Re: [DOCS] Streaming replication document improvements From: Robert Haas To: Fujii Masao Cc: Heikki Linnakangas , PostgreSQL-development , pgsql-docs@postgresql.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.6 tagged_above=-10 required=5 tests=AWL=-0.762, BAYES_00=-2.599, FS_REPLICA=1.041, SARE_SPEC_REPLICA=0.72 X-Spam-Level: X-Archive-Number: 201003/1329 X-Sequence-Number: 160105 On Wed, Mar 31, 2010 at 9:58 PM, Fujii Masao wrote: > On Thu, Apr 1, 2010 at 10:52 AM, Robert Haas wrot= e: >> On Wed, Mar 31, 2010 at 9:50 PM, Fujii Masao wro= te: >>>> That's an interesting point, do streaming replication connections >>>> consume superuser_reserved_connections slots? >>> >>> Yes. Since SR connection is superuser connection, setting >>> superuser_reserved_connections appropriately would be useful >>> to prevent non-superuser connections from blocking the connection >>> from the standby. >> >> I think this is wacky, especially since we'd someday like to have >> replication be a separate privilege from superuser. =A0I think we should >> change this. > > You mean that we should change replication connection not to consume > superuser_reserved_connections slots in 9.0? Yes. ...Robert