Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tYnTu-00FLlw-Uo for pgsql-general@arkaria.postgresql.org; Fri, 17 Jan 2025 14:37:55 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tYnTt-00H8AG-48 for pgsql-general@arkaria.postgresql.org; Fri, 17 Jan 2025 14:37:53 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tYnTs-00H880-OH for pgsql-general@lists.postgresql.org; Fri, 17 Jan 2025 14:37:53 +0000 Received: from mail-ed1-x52c.google.com ([2a00:1450:4864:20::52c]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tYnTo-0002F0-1O for pgsql-general@lists.postgresql.org; Fri, 17 Jan 2025 14:37:49 +0000 Received: by mail-ed1-x52c.google.com with SMTP id 4fb4d7f45d1cf-5d88c355e0dso4233685a12.0 for ; Fri, 17 Jan 2025 06:37:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1737124665; x=1737729465; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=bfICVonYYG9S5NQjxQtFMRoTTyuiACnBB7COCKnyBQs=; b=K9ik5DM83hx1m+475HjwJMdjdWjRrGvsFllxEmAs1az3kuMu6X0+FJFAG6kD+/L6HF vld+eoI/34OYYobpudgRZQA5tkVH4shX815LpbeEPshk/yMwiQ8zZADjNdD1H9ShEE0m 3tSDxFI5bPl6rvYLN2xh0wSf+bY13NzvaBVLSwzkjngBs1UYlapNI1Anx3tNDaXUyPOm xjjVuxl74uU2qlvFgZ9eJ4p5Sxnzc9R2//j6aoLblJQ3ymrsstB6AE83lho2h6F2HRcB HXB5OKK23VzaFphi0KOlGiuj84KrM51ajiSpELrKk4dMOtq0EW3sUeRzCpcqx5mFLkxm o+5A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1737124665; x=1737729465; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=bfICVonYYG9S5NQjxQtFMRoTTyuiACnBB7COCKnyBQs=; b=PggXtpnBCB+Fp4Kl1jzvfSAIFOOAxcp/isM64uQllhEhoUDozPAT4vEWfWoBsZDM64 Lf49ikojnEGk0b1+lDeQv4Z1gxQpvxRqg+6TOvM/RYkLU9DTyWwGrDgLmBg/1aQK6stU tEv/iJHjipvVmhSAxy3pzSvzIY8rpGetFPht/QQnEk/eDRp/iSPd4tRWul9uFueJJ5AH VXD2XQJ9Vek+XXaPD5zGJlEyPfUeBYwIEAWoAVOUndxrrJ0frITg339esPU1wmk2s7k2 20o5WW04BvpR7ntIkEVUZR0dYwgesTe/3ihUFktiQ6B2Pj2xmEegnnQP6CyGrcstYj9A WP7g== X-Gm-Message-State: AOJu0YyIx67OXbMH5Ukd8VgrjXuP8J6/u/daAmWha781cJB2rFWAWSay of2eWjHbx9LAaaJG7UBAur9DKLXSkaacs7gInc9FWmcam5RIi/lpyulfayQ4Wte+0N0E6W9VUnP ibSqJW7+dgyfUcfV1AED0VwQoovDPq45C X-Gm-Gg: ASbGnctT4wsJWXYCjrVQTl7zbEc+Br9c4UYJalxUibpTz9xndrCDdr16XgFB9y8ZYC5 D7dJ7u4DUT0xwXYTR7geRnEuf9WjtdXfA+vSkPQ== X-Google-Smtp-Source: AGHT+IHSED5VzVFiQYvAzUvEZjsMEk6PY30zgEzbnVqDU8LswJVjVyMZsmNZmYd5a7km3UdlxOdlGqPcoip2mJqsO44= X-Received: by 2002:a17:907:7faa:b0:a9e:b150:a99d with SMTP id a640c23a62f3a-ab38b1b45aamr290134666b.5.1737124665349; Fri, 17 Jan 2025 06:37:45 -0800 (PST) MIME-Version: 1.0 From: Franjo Stipanovic Date: Fri, 17 Jan 2025 15:37:34 +0100 X-Gm-Features: AbW1kvaNr3La5TWD9EU_rN2TkrU-7PebwXV3bhSSvZ73CHyTZw_XvS5DYN09US8 Message-ID: Subject: Different Autovacuum Settings on Master and Replica in Streaming Replication To: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="0000000000009bde04062be7dadf" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000009bde04062be7dadf Content-Type: text/plain; charset="UTF-8" Question regarding autovacuum settings in a PostgreSQL streaming replication setup. Specifically, I am curious about whether it is possible (and advisable) to have different values for the following settings on the master and replica databases: - autovacuum_vacuum_scale_factor - autovacuum_analyze_scale_factor Can the above settings be configured differently on the master and replica databases in a streaming replication setup? I just tested this on AWS RDS Postgres. How would those different settings interact with replication, for example, if I apply change on master, would it be replicated to replica and override my replica setting? I was expecting that this is not possible in streaming replication, only in logical replication. Thank you! --0000000000009bde04062be7dadf Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Question regarding autovacuum settings in a PostgreSQL = streaming replication setup. Specifically, I am curious about whether it is= possible (and advisable) to have different values for the following settin= gs on the master and replica databases:
-=C2=A0autovacuum_vacuum_scale_f= actor
- autovacuum_analyze_scale_factor

Can the above settings be = configured differently on the master and replica databases in a streaming r= eplication setup? I just tested this on AWS RDS Postgres.=C2=A0

How w= ould those different settings interact with replication, for example, if I = apply change on master, would it be replicated to replica and override my r= eplica setting?=C2=A0

I was expecting that this is not possible in st= reaming replication, only in logical replication.

Thank you!

--0000000000009bde04062be7dadf--