Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cgC1b-0000YX-Rt for pgsql-admin@arkaria.postgresql.org; Tue, 21 Feb 2017 15:06:43 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cgC1b-0004N9-A9 for pgsql-admin@arkaria.postgresql.org; Tue, 21 Feb 2017 15:06:43 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cgC1a-0004Mm-MW for pgsql-admin@postgresql.org; Tue, 21 Feb 2017 15:06:42 +0000 Received: from mail-vk0-x243.google.com ([2607:f8b0:400c:c05::243]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1cgC1Y-0004YZ-Eg for pgsql-admin@postgresql.org; Tue, 21 Feb 2017 15:06:41 +0000 Received: by mail-vk0-x243.google.com with SMTP id t8so10703738vke.0 for ; Tue, 21 Feb 2017 07:06:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:references:in-reply-to:subject:date:message-id:mime-version :thread-index:content-language; bh=2dzdf7TmwWBhVO/bt0Qx+FWrqMUxiacdYfLYIt9AyuI=; b=rL0kp5F2mHaFMPGMuuMIz+y/ZgP79Qw/UWj/dkp+7J2F9UMEIYiJZ2GoyBVh/dSHeq kpFx8E6Wm34/lpV1K2uaBubtKFNDQCadfkqkk7Zsp7bs96PM3TghZGMhUgf9uXf3q0zo 0UBCZU7DNfZkeo6vSfn0QOB0kZ60cIrHqzthXg0qo46pdMb4xjAHfEIIQoTdAPd2a5Uu b24j+AiL8WanTCfClE51mMgEbVGFkaC2DBVXEeIcKYYCMa9ABSGh4ChuteXgKuInIZz/ 7FnC7BDnSL6DceZqk7pXQ4c8In4tSN0W8jSVIuTzRdLt4RSjkqBPZe0kLt2auASWN0ZP 7fHQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:references:in-reply-to:subject:date :message-id:mime-version:thread-index:content-language; bh=2dzdf7TmwWBhVO/bt0Qx+FWrqMUxiacdYfLYIt9AyuI=; b=EUm4Q/XtFXLvkR7wpnyGXOrNV487Qq/GqBRLCQxqtVCWqYUe2+Za3Z14UKXHyUf976 YZ2vpCeqaJMBN9NMXqMdDRsRH75aEFizxE+MH6F35RW+3OW9SIQgm7kW7g9U05gPBymt Xhwdtl5zBhjckD/1q55/qHcdavXpRUv1tN4VVKO4lGC9x5dpSW1S25tjUY25P8TpMUcx aJgakCaFwhIxNbgTuPmBNtEVVkQk0F982T8M2yxKiiytkoEmXTwcZ/CYlzDhkjCI3qmg I4Sh4DKuLNm8FuplSmd5RZInonEdk4Yg6Fj4EACDriQdd1f9L5JD81ltIS1BNjhQih4y dLUQ== X-Gm-Message-State: AMke39lsx5KR7kL35XPPYmO+ea5n3Jyz8HMcGUpD8iwQRL07eBNxKWKG0eor6XSg6IhyKQ== X-Received: by 10.31.27.79 with SMTP id b76mr13245146vkb.168.1487689599371; Tue, 21 Feb 2017 07:06:39 -0800 (PST) Received: from irylachi ([200.55.161.75]) by smtp.gmail.com with ESMTPSA id l30sm5604579ual.37.2017.02.21.07.06.36 (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 21 Feb 2017 07:06:38 -0800 (PST) From: "Lazaro Garcia" To: =?UTF-8?B?J86azr/Ous68zqzOtM63z4IgzpTOt868zq7PhM+BzrnOv8+CJw==?= , References: <5891C050.3060100@matrix.gatewaynet.com> <5891CB47.2090104@matrix.gatewaynet.com> In-Reply-To: Subject: Re: Big sized materialized views break replication Date: Tue, 21 Feb 2017 10:06:41 +0100 Message-ID: <001501d28c21$d2ad0710$78071530$@gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0016_01D28C2A.34716F10" X-Mailer: Microsoft Outlook 15.0 Thread-Index: AQD1xkNLjjhFPgJyJmU9otcXXllRKQGUmDeVAW4I654B8TM1UgDkDWp3ov3zqNA= Content-Language: es-mx X-Pg-Spam-Score: -0.9 (/) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org This is a multipart message in MIME format. ------=_NextPart_000_0016_01D28C2A.34716F10 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable If recovery.conf has this configuration parameter: =20 primary_slot_name =3D repmgr_slot_1 =20 The replication use replication slots otherwise when wal_keep_segments = is reached, the redo logs are rotated. =20 With replication slot you only have the required wal files but with = wal_keep_segments you only has the amount especified in it. =20 If you do not use replication slots there is no need of creating slots, = see SELECT * from pg_replication_slots; on the master. =20 When a slot is used, wal_keep_segments has no effects and could be 0. =20 Regards. =20 De: pgsql-admin-owner@postgresql.org = [mailto:pgsql-admin-owner@postgresql.org] En nombre de ???=C2=B5?d?? = ??=C2=B5?t???? Enviado el: martes, 21 de febrero de 2017 08:23 a. m. Para: pgsql-admin@postgresql.org Asunto: Re: [ADMIN] Big sized materialized views break replication =20 Hello, =20 Is it possible to use replication with slots and without them in the = same setup or it could cause a problem? =20 Regards, Dimitris=20 ------=_NextPart_000_0016_01D28C2A.34716F10 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

If recovery.conf has this configuration = parameter:

 

primary_slot_name =3D = repmgr_slot_1

 

The replication use replication slots = otherwise when wal_keep_segments is reached, the redo logs are = rotated.

 

With replication slot you only have the = required wal files but with wal_keep_segments you only has the amount = especified in it.

 

If you do not use replication slots there = is no need of creating slots, see SELECT * from pg_replication_slots; on = the master.

 

When a slot is used, wal_keep_segments has = no effects and could be 0.

 

Regards.

 

De:<= /b> = pgsql-admin-owner@postgresql.org = [mailto:pgsql-admin-owner@postgresql.org] En nombre de = ???=C2=B5?d?? ??=C2=B5?t????
Enviado el: martes, 21 de = febrero de 2017 08:23 a. m.
Para: = pgsql-admin@postgresql.org
Asunto: Re: [ADMIN] Big sized = materialized views break replication

 

Hello,

 

Is it possible to use replication with slots and = without them in the same setup or it could cause a = problem?

 

Regards,

Dimitris 

<= /html> ------=_NextPart_000_0016_01D28C2A.34716F10--