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 1frhtH-0007CB-1D for pgsql-admin@arkaria.postgresql.org; Mon, 20 Aug 2018 10:58:31 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1frhtF-0006TP-1U for pgsql-admin@arkaria.postgresql.org; Mon, 20 Aug 2018 10:58:29 +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 1frhtE-0006TI-Qe for pgsql-admin@lists.postgresql.org; Mon, 20 Aug 2018 10:58:28 +0000 Received: from hermes.gatewaynet.com ([193.92.121.98]) by magus.postgresql.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1frhtA-0008M0-VI for pgsql-admin@lists.postgresql.org; Mon, 20 Aug 2018 10:58:28 +0000 Received: from smadev.internal.net (pc131.internal.net [10.9.200.131]) by hermes.gatewaynet.com (8.14.3/8.14.3/Debian-9.4) with ESMTP id w7KAw935013996 for ; Mon, 20 Aug 2018 13:58:14 +0300 Received: from smadev.internal.net (smadev [10.9.200.131]) by smadev.internal.net (8.15.2/8.15.2) with ESMTP id w7KAw7Lv063546 for ; Mon, 20 Aug 2018 13:58:07 +0300 (EEST) (envelope-from achill@matrix.gatewaynet.com) Subject: Re: logical Replication To: pgsql-admin@lists.postgresql.org References: <1534748661624-0.post@n3.nabble.com> <17b9b7a5-5377-b904-0e8a-e72e72efe1ef@matrix.gatewaynet.com> <1534750828102-0.post@n3.nabble.com> <11f06cb4-8e48-7090-76e0-438b54c70660@matrix.gatewaynet.com> <1534751989163-0.post@n3.nabble.com> <1534755490841-0.post@n3.nabble.com> <901cba81-3658-2cf1-25e5-1a20460b9e48@matrix.gatewaynet.com> <1534759670437-0.post@n3.nabble.com> <1534761445109-0.post@n3.nabble.com> From: Achilleas Mantzios Message-ID: Date: Mon, 20 Aug 2018 13:58:07 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <1534761445109-0.post@n3.nabble.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Virus-Scanned: clamav-milter 0.98.7 at hermes X-Virus-Status: Clean X-Spam-Status: No, score=-27.0 required=5.0 tests=ALL_TRUSTED,DYN_HAM_COORD, DYN_HAM_IT,DYN_HAM_NAUTICAL,DYN_HAM_SIGNAT1,DYN_SPAM_MED6 autolearn=unavailable version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on hermes.gatewaynet.com List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 20/08/2018 13:37, pavan95 wrote: >> If you are marginal on space available, the slightest delay can cause the > replication slot to run out of space. >> So increase your space. > How can I judge myself that marginal space is left available. But the fact > is I do still have 50 GB of additional disk space available(on the mount > point where the postgres 10.4 data directory runs) when I issued "df -kh" . > > So I need to have a valid justification in order to ask the systems team for > space getting added. But still I'm unable to find any reason from our > conversation. "No space left on device" is a big reason. This is alarming. Your sysadms should have had monitoring in place and should have addressed and resolved this already. > > But the point I wonder is the snaps are getting automatically deleted and > the error stops producing for a period of time. Looking forward to touch the > pain area(if at all the server feels). > > Looking forward to hear from you. Thanks in Advance. > > Regards, > Pavan > > > > > > -- > Sent from: http://www.postgresql-archive.org/PostgreSQL-admin-f2076596.html > -- Achilleas Mantzios IT DEV Lead IT DEPT Dynacom Tankers Mgmt