Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jRJMa-0002pM-6l for pgsql-docs@arkaria.postgresql.org; Wed, 22 Apr 2020 17:40:44 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jRJMX-00087f-7v for pgsql-docs@arkaria.postgresql.org; Wed, 22 Apr 2020 17:40:41 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jRJMX-00087Y-0k for pgsql-docs@lists.postgresql.org; Wed, 22 Apr 2020 17:40:41 +0000 Received: from mail-qv1-xf41.google.com ([2607:f8b0:4864:20::f41]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jRJMQ-0001m7-85 for pgsql-docs@lists.postgresql.org; Wed, 22 Apr 2020 17:40:39 +0000 Received: by mail-qv1-xf41.google.com with SMTP id bu9so1285862qvb.13 for ; Wed, 22 Apr 2020 10:40:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:subject:message-id:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=RaieCR+iTCJP4PceBJ7fPPUhgi0W1BJC1YVMFZFGtR0=; b=Ve4nbC2l4hR3JaXP9TwFe6NHnK0f6UZ4+CjwcimqahvZHAbWKxgzud/WAfX8sBs26z 2lNeByE41koJ0uUg//QiKJMRi2cgSGLezP0nrUY2oly4OsnIYTIa0kmkJWTmB6d/IBt+ hOZqYEdCPrar0ZJZWMZQ5BnWYkauZ3fwLGJEQxHi0HDasAblMwvh+MC+ez6MWX2oLBsg LnUIBWS54fSERYQkkWnmYMFyp9+QwmvIZ7lE5O6MQohxy4FFNhNi+Bv8g89nwvEsuC4K x274gSnBEumi425YS4AXu2OI2wRIUBTfUc/gELj+uF3Df05S0ZBOGLzNwwgXfhUnZivo Kddg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=RaieCR+iTCJP4PceBJ7fPPUhgi0W1BJC1YVMFZFGtR0=; b=NC89X9PrNIclHVHmcs8yWK2sIQYdXx6oed4hEGL7t+IRhy2HuE39C77bJJ4jcMo7ft LVyebRwqKbJ90s0auIdDTCTgk7TNhXVOzgdmGm6lmDBe/pBiPt0NEMRAKZO/g0ReN86M a/7ajWM7TZjmjBnkTmVxbjzc2DqIrMf/5W56u+urPOvGQGvmm5jVoS9sPqjMtzEIWriV ixLP+hfPkHcnECpznaXn/ZxJ9KVKCl8wxB5Gx9uFQZO4nDORkWHJDbwRHGuS4UHODScg ISW3A6po+LeyHWeg/7duKYOPWCzggWkN6y+bxznBGwMdhpBYSRMDr9GAnA5xABsfaktr lUfQ== X-Gm-Message-State: AGi0PuZ8hz2vFlBlZajhWXgA4aeqWTIkfu9hkkJCHcXfa5XOW7zUQbd4 qkCagw7TdZljVBZwctscXz6TS7iu94HWuv36mQ2LRqdErLXLFml8/cycFHegFSf83XU1DCOGQCy eA/LZncMAgXe1k+NiMdWS3cOo+qUpg9zupuHEubGDR6IwVWJTVIKDmba65Eo69AFyA6fJ5kdMyC Lk9vhWAkRpnYYO X-Google-Smtp-Source: APiQypIIFx0ZMz9DCPF0zg2i2fUo+hLwumj8dnw+oLV8h76GXoLV9NAYI+hTF7g7SDh9YGkxHKKcgA== X-Received: by 2002:ad4:4462:: with SMTP id s2mr26151023qvt.221.1587577232530; Wed, 22 Apr 2020 10:40:32 -0700 (PDT) Received: from nimloth.alvh.no-ip.org ([190.95.18.252]) by smtp.gmail.com with ESMTPSA id y18sm4743906qty.41.2020.04.22.10.40.31 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 22 Apr 2020 10:40:32 -0700 (PDT) Received: by nimloth.alvh.no-ip.org (Postfix, from userid 1000) id CEF7F30142C; Wed, 22 Apr 2020 13:40:29 -0400 (-04) Date: Wed, 22 Apr 2020 13:40:29 -0400 From: Alvaro Herrera To: chris+postgresql@qwirx.com, pgsql-docs@lists.postgresql.org Subject: Re: Logical replication subscription owner Message-ID: <20200422174029.GA17052@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <158695933852.25700.8124720971187835491@wrigleys.postgresql.org> User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2020-Apr-15, PG Doc comments form wrote: > If the logical replication subscription is owned by a role that is not > allowed to login (for example, if the LOGIN privilege is removed after the > subscription is created) then the logical replication worker (which uses the > owner to connect to the database) will start to fail with this error > (repeated every 5 seconds), which is pretty much undocumented: > > FATAL: role "XXX" is not permitted to log in > LOG: background worker "logical replication worker" (PID X) exited with > exit code 1 > > You might want to include that error message in the docs, to ensure that web > searches for it bring the user to this documentation. I wonder if a better answer is to allow the connection when the REPLICATION priv is granted, ignoring the LOGIN prov. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services