Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1ft0AE-00040I-Ha for pgsql-docs@arkaria.postgresql.org; Fri, 24 Aug 2018 00:41:22 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1ft0AB-0001fL-Nq for pgsql-docs@arkaria.postgresql.org; Fri, 24 Aug 2018 00:41:19 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1ft0AB-0001fE-IG for pgsql-docs@lists.postgresql.org; Fri, 24 Aug 2018 00:41:19 +0000 Received: from mail-qk0-x244.google.com ([2607:f8b0:400d:c09::244]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1ft0A7-0006do-Hu for pgsql-docs@lists.postgresql.org; Fri, 24 Aug 2018 00:41:18 +0000 Received: by mail-qk0-x244.google.com with SMTP id 89-v6so4878400qkp.2 for ; Thu, 23 Aug 2018 17:41:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=to:from:subject:openpgp:message-id:date:user-agent:mime-version :content-language:content-transfer-encoding; bh=7HT1M+4OgSBvEpSi6wqjyv6PCbJt6ntXfqu+ZEpZEcQ=; b=guImA9twoGESdySHdNUkcjw91A2JGGdFuxk+23ukQLz5JjSsKoGYKtFKfDud+K3qDG AmiahGiNB5k+IXYHNoWq7QQz2DUXXP13jp2JXh2chq05T8pNfYKk3geG2nAld4h/Ru9i jJBUlIdppk3rm+bij7fljpsC21eV5E9JgkCh7oFL3QYIGyY6426IGyl+ge38AIuug5sb xOIENxlCKTAWJi3MyK5rgLb7TWhndOPj4HGIojhx9kTEgPey0Tg/4yP3EjDzfzHECrJd cpP5BViWaa3aUQ6p9AL/+XBZuaIqP9vfblTPys+xRhE6M4ztcWbbsGuM4EqqtfdUam1R Tf3Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:openpgp:message-id:date :user-agent:mime-version:content-language:content-transfer-encoding; bh=7HT1M+4OgSBvEpSi6wqjyv6PCbJt6ntXfqu+ZEpZEcQ=; b=Wu5dZ0VoN6uWi8l2c3dwSsR2asCanU6gavvAR/hSuD8S0Si5NiQ2UIA/P/b26g4dXv WrBJDDAWicBwXliTnPVALGwqYqs7Gerzrs00ZWcmverrvLOK09n/Ah541XU0frK2hGvu 4S8QDAJ0pdrtH/ryu4JyAldZ/7JJ3cIeHdXOrVr++l9qY433GwmXMOWqGKR9M7LSmS34 VSdZvF+i6q21l5RcNim7zKOr28h1br0j1XDzmMLBp8OwhQTcsShS+msj2eW2/AiOQcZO dCzubc74/Bsc1ZMs3AjwFjjAzR3tgTAjbN4I171eJ9pCJT+ygeyNSTRryNsa6Hm58V/W 4UEw== X-Gm-Message-State: AOUpUlG6TkSEYk0HIBgZOlHuybYoxoAJgMtJrRR1CabBPo0GBzvrJD1Z 7lK/wo7L8xUvThCp3km0YaWYbQTip1JYnmWFD4mfg2kkHVmsuefCMjsKdMCUfLhZafmR9erGjeZ Xgh5PpRDjLkMlUHWCmD5oSak4ksgR6LtCqOMJuSYFe0/8oWXRlLmV6VUs2D3QrwaUitZfGcFzxG rfP+iKShafd/MiX54uMA== X-Google-Smtp-Source: AA+uWPyd45bOB5eADNCYASl4Qi++Zp1vR8ZQwomlWNA9AoyJj+dOhgg45p1NXYpsT4LMdEW/aDBxrg== X-Received: by 2002:a37:f50f:: with SMTP id l15-v6mr57589873qkk.251.1535071270489; Thu, 23 Aug 2018 17:41:10 -0700 (PDT) Received: from alderaan.marques (host114.200-117-46.telecom.net.ar. [200.117.46.114]) by smtp.googlemail.com with ESMTPSA id r10-v6sm3861567qtj.41.2018.08.23.17.41.09 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 23 Aug 2018 17:41:09 -0700 (PDT) To: pgsql-docs@lists.postgresql.org From: Martin Marques Subject: replication slots only need user with replication for creation Openpgp: preference=signencrypt Message-ID: <9e656b3b-0a18-780c-6bca-7270463a2128@2ndquadrant.com> Date: Thu, 23 Aug 2018 21:41:07 -0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hi, Looking at privileges that a user would need now a days to create a cluster clone with repmgr we noticed that there's inaccurate information in the docs regarding the use of replication functions. I was able to test on 9.6 and 10 that a user with replication privileges can create and drop a replication slot. But in the system administration functions, section replication functions it states: The functions shown in Table 9.83 are for controlling and interacting with replication features. See Section 26.2.5, Section 26.2.6, and Chapter 49 for information about the underlying features. Use of these functions is restricted to superusers. Source: https://www.postgresql.org/docs/10/static/functions-admin.html#FUNCTIONS-REPLICATION I suggest amending this with a text like the following: The functions shown in Table 9.83 are for controlling and interacting with replication features. See Section 26.2.5, Section 26.2.6, and Chapter 49 for information about the underlying features. Use of these functions is restricted to superusers and users with replication privileges. I think this doc patch should be back-patched Regards, -- Martín Marqués http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services