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 1tBG2L-002kzL-VM for pgsql-general@arkaria.postgresql.org; Wed, 13 Nov 2024 16:16:09 +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 1tBG2J-00FOV6-4m for pgsql-general@arkaria.postgresql.org; Wed, 13 Nov 2024 16:16:07 +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 1tBG2I-00FOUw-Pk for pgsql-general@lists.postgresql.org; Wed, 13 Nov 2024 16:16:07 +0000 Received: from mail-lj1-x22a.google.com ([2a00:1450:4864:20::22a]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tBG2C-001k7a-Vp for pgsql-general@postgresql.org; Wed, 13 Nov 2024 16:16:06 +0000 Received: by mail-lj1-x22a.google.com with SMTP id 38308e7fff4ca-2fb3c3d5513so64783621fa.1 for ; Wed, 13 Nov 2024 08:16:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1731514561; x=1732119361; darn=postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=CiMIMNxl+OL/tVBWtmt2Jq+mbSIW13vpfaCBk9CbW/4=; b=Hu6wTGFMJpqoOWGz/z0rKejdcJ2Htydp+oJvwVtsKgHWlG2zrxxKCYDtGUdo5a0aNa nrN2Fht3M6X4HsQdh/Gy8EOixHBYJ4sj3a2BUfFu0BGKvwd2fQdpzbJJ+YHen5FhUVfE Q2BbRE2GYwIHOs/ZBA993f4f8Eh9ipVhtli2jHXxK6RkYcCp2FCasWnwfxDfjGUTrb4d kge/9I6tKWQsvhkruVM2e5ePuy8vVj5qP6AjdlJ24LBGi6m8l3zy3YT2h4yUZVlkEPQU jSuzRFW5UoT38Nx81O3VU5CV9Xw3k0Ylu2Sg6gdV8HAvsK0K0Rz3APicWdur0nLrr2By rkwA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1731514561; x=1732119361; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=CiMIMNxl+OL/tVBWtmt2Jq+mbSIW13vpfaCBk9CbW/4=; b=uMX0+7LFOi9w7M+DzgrnxpKhfz0PL8Td7qPUCFM+RpstUtOJ1kHnNC71dDAlI+h2O9 a0SBkoSWloLjP15kwuKLltnOBSStgQ6M5QbxQeaZ9R1Cj2VtVlhbjcfdnjfCe1vJHg/K 6n2PImXfsJEECRRRYvnegGUlA8n73lI7GSU6tMv6il+LBJ7Zy9/Vj+9oerKlWVKvT+KE efmnMxaNvQX2fmvK/QxMFBYCuClDv3H9um+Gv1N+fstweZtP8XcqVkpZr2YD3bC/H6k8 zsGoEspT7kPMbBnmBsL89mhracGZEhiBayfo7/sFdGrjOxQpJhmUO5gHgDoFnSiZQPrc ZKtg== X-Gm-Message-State: AOJu0YzaPwIJmmZcoE1WlF4hbAgss+DsMV0P4W+DAN+xd8DRTRpmu8PU wuvmx3uHGs2Mh1hknY4ekHHfYX10uuhJ0gIeXGcxOWIFtVS6vaNMrGajjNGCgzvjXyonpgITxfK +t3liHxGoxCOoR2uba6v0uAWM/yU+8nvo X-Google-Smtp-Source: AGHT+IEH/B8/27C2sPZDZnlkJ7bb7G2NjRykgp4FtTdKRYe1qj7xcILD7F6e1RV3qDN/5KfscPbKsyYItJu0R2vpGSU= X-Received: by 2002:a05:651c:2228:b0:2fb:6394:d6bd with SMTP id 38308e7fff4ca-2ff4c5bf80dmr17562631fa.12.1731514560411; Wed, 13 Nov 2024 08:16:00 -0800 (PST) MIME-Version: 1.0 From: jayakumar s Date: Wed, 13 Nov 2024 21:45:49 +0530 Message-ID: Subject: DB wal file disabled --_Query To: pgsql-general@postgresql.org Content-Type: multipart/alternative; boundary="0000000000004bfd290626cda6d8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000004bfd290626cda6d8 Content-Type: text/plain; charset="UTF-8" Hi Team, We have disabled walfile ion database level. While I do manual switch wal file generating in wal file location. Here is my question if we disable it. Walfile won't generate am i correct? Kindly clarify my doubts. postgres=# select name,setting from pg_settings where name like 'archive%'; name | setting -----------------+------------ archive_command | (disabled) archive_mode | off archive_timeout | 0 (3 rows) postgres=# postgres=# SELECT pg_switch_wal(); pg_switch_wal --------------- D/9D000000 (1 row) [postgres@xxxxxxxxx pg_wal]$ ls -lrt total 81920 drwx------. 2 postgres postgres 6 Oct 13 2020 archive_status -rw-------. 1 postgres postgres 16777216 Nov 13 20:47 000000010000000D0000009F -rw-------. 1 postgres postgres 16777216 Nov 13 20:50 000000010000000D000000A0 -rw-------. 1 postgres postgres 16777216 Nov 13 20:51 000000010000000D000000A1 -rw-------. 1 postgres postgres 16777216 Nov 13 21:02 000000010000000D0000009D -rw-------. 1 postgres postgres 16777216 Nov 13 21:02 000000010000000D0000009E [postgres@# pg_wal]$ --0000000000004bfd290626cda6d8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Team,

We have disabled wa= lfile ion database level. While I do manual switch wal file generating in w= al file location.

Here is my question if we disabl= e it. Walfile won't generate am i correct?

Kin= dly clarify my doubts.

postgres=3D# select nam= e,setting from pg_settings where name like 'archive%';
=C2=A0 = =C2=A0 =C2=A0 name =C2=A0 =C2=A0 =C2=A0 | =C2=A0setting
----------------= -+------------
=C2=A0archive_command | (disabled)
=C2=A0archive_mode = =C2=A0 =C2=A0| off
=C2=A0archive_timeout | 0
(3 rows)

pos= tgres=3D#

postgres=3D# SELECT pg_switch_wal()= ;
=C2=A0pg_switch_wal
---------------
=C2=A0D/9D000000
(1 row)<= /div>

[postgres@xxxxxxxxx pg_wal]$ ls -lrt
total 8192= 0
drwx------. 2 postgres postgres =C2=A0 =C2=A0 =C2=A0 =C2=A06 Oct 13 = =C2=A02020 archive_status
-rw-------. 1 postgres postgres 16777216 Nov 1= 3 20:47 000000010000000D0000009F
-rw-------. 1 postgres postgres 1677721= 6 Nov 13 20:50 000000010000000D000000A0
-rw-------. 1 postgres postgres = 16777216 Nov 13 20:51 000000010000000D000000A1
-rw-------. 1 postgres po= stgres 16777216 Nov 13 21:02 000000010000000D0000009D
-rw-------. 1 post= gres postgres 16777216 Nov 13 21:02 000000010000000D0000009E
[postgres@#= pg_wal]$
--0000000000004bfd290626cda6d8--