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 1t0l4n-00D2xh-8g for pgsql-general@arkaria.postgresql.org; Tue, 15 Oct 2024 17:11:17 +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 1t0l4l-0094C6-CA for pgsql-general@arkaria.postgresql.org; Tue, 15 Oct 2024 17:11:15 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t0l4l-0094Bw-0I for pgsql-general@lists.postgresql.org; Tue, 15 Oct 2024 17:11:15 +0000 Received: from mail-yw1-x112b.google.com ([2607:f8b0:4864:20::112b]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1t0l4e-001DPj-Qs for pgsql-general@postgresql.org; Tue, 15 Oct 2024 17:11:14 +0000 Received: by mail-yw1-x112b.google.com with SMTP id 00721157ae682-6e214c3d045so42527877b3.0 for ; Tue, 15 Oct 2024 10:11:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1729012267; x=1729617067; darn=postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=JVa1DkoblKfYbUHQGLO1dFBjfsCB3dIJ3raRstzaLm4=; b=O5b7ffXCfQKFpQcU8QMa2qCkeZqTbKfj4jP40br1zLmCAB/k1X+ekKB6R+5x6bgC8d fPao893e+ExFlzRuREktd2alryubwBnRdbeqed61KDp82Hqfyv2/RlrC9ctVYIcsYjvF csLz3S7s8ky27OcwRnKZHgoRljSna5plfWhGY90zD2S06tll6gzdaZzf7n39iabDSkYo 8X9BPXRPxkMcVTy8cfp9Pgll5avlRTmRyUhX72ZGTV8wzAzcykiDj+oRwdwpk1KtD959 I/38fK+bZcdpXtARqACHB2owcU0/F74WI7MyXSV93Gp5W+rUMRw6dgb2a1FCuO1k8Xgz RrvQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1729012267; x=1729617067; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=JVa1DkoblKfYbUHQGLO1dFBjfsCB3dIJ3raRstzaLm4=; b=NgeER5zJkh45Ef7K6iM44/Cg82PMVEHoB6BaRFPp/h4ajAl0EfWgk8y362PduKp2mZ Yq2eEMK3DBKnWs+YUjE28hAXuL9RI1YABFRgWo1sqwxzy2xw9W7Qsg9sFj8W+0+qKlYY K6P9lJFY26kHntpsiSOewO8EGNoIvAascQYKnSXJy0qb2j8EgVAKLDBLPFL0C4xYhWPQ 0m1E926S+Db+NIA0Wrpcj0sJkn7ljbb55Gk1w1FVuZivGU0q0Z7bLLCV2RRMUmmeT7+R A1xH9X8R9lgTNmNi6x8HuMrgZDECQi5Q0JWWjFnNx0zPvrInyjpI1f3j/GfGye2qIqHc 9iTw== X-Gm-Message-State: AOJu0YwkokAR/LZcMF76VH0pzswhbadY+EwnhFzEQDolaMWnKq21/23v 1sZ5ERjUX/K8UIenyhSFZlgJGRu58bog84MDqtc7NdxzW7WemmQyvBIk2ZB8HF6kLUNKcnHwvr1 Pe2Gtzt7IrdFipEZI4Ip083BOqjXkmdxf X-Google-Smtp-Source: AGHT+IFM02HesKrzCUX3/AdwY5SGEkspc3f31b5T98XxJ/BMpPK0Ay5XvrbsNKiMrpLKX0rthFo8oIas+GcJYd+FerM= X-Received: by 2002:a05:690c:83:b0:6e2:313a:a01e with SMTP id 00721157ae682-6e3643a5fa5mr104990697b3.32.1729012266924; Tue, 15 Oct 2024 10:11:06 -0700 (PDT) MIME-Version: 1.0 From: KK CHN Date: Tue, 15 Oct 2024 22:40:53 +0530 Message-ID: Subject: WAL replication standby server: query To: pgsql-general Content-Type: multipart/alternative; boundary="000000000000fb849106248709cc" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000fb849106248709cc Content-Type: text/plain; charset="UTF-8" List , I am trying to configure a WAL replicated standby server(EDB16) .. In the archive command I used a dedicated "/data/archive " directory for WAL archiving as follows, as I don't want any WAL overwriting in the default WAL directory and loss of WAL files. I have archive_command= ' cp %p /data/archive/%f ' pg_hba.conf I have host replication all 10.255.10.0/24 md5 My doubt is whether the standby Postgres server(EDB16) reads WAL files by itself from the primary server's explicit WAL archive folder /data/archive by its own ? OR The standby can read only from the default WAL location ie; pg_wal directory of primary server ? Please enlighten me. If the standby can read only the default pg_wal folder, then how can we make the standby server to read from the explicit " /data/archive " folder for WAL syncing automatically to the standby ? Any input is much appreciated. Thank you, Krishane --000000000000fb849106248709cc Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
List ,

I am trying=C2=A0=C2=A0to=C2=A0 = configure a WAL replicated=C2=A0 standby server(EDB16) ..=C2=A0 =C2=A0In th= e archive command=C2=A0 I used a dedicated=C2=A0 "/data/archive "= directory=C2=A0 for WAL archiving as follows, as I don't want any WAL = overwriting in the default WAL directory and loss of WAL files.=C2=A0
=

I have
archive_command=3D=C2=A0 ' cp %p /= data/archive/%f '

pg_hba.conf=C2=A0 =C2=A0= I have

host=C2=A0replication =C2=A0 =C2=A0 all = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 10.255.10.0/24=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 md5

My doubt is whether=C2=A0the standby Postgres server(= EDB16) reads WAL files by itself=C2=A0 =C2=A0from the primary server's= =C2=A0 explicit WAL archive folder /data/archive=C2=A0 by its own=C2=A0 ?= =C2=A0
OR
=C2=A0 The standby can read=C2=A0 only from t= he default=C2=A0WAL location=C2=A0 ie; pg_wal=C2=A0 =C2=A0directory of prim= ary server ?=C2=A0

Please=C2=A0 enlighten me.

If the standby can read only the default=C2=A0pg_wal f= older, then how can we make the standby server to read from the explicit=C2= =A0 " /data/archive "=C2=A0 folder for WAL syncing automatically = to the standby ?

Any input is much=C2=A0appreciate= d.

Thank you,
Krishane
--000000000000fb849106248709cc--