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 1tNqu9-002Znk-GK for pgsql-general@arkaria.postgresql.org; Wed, 18 Dec 2024 10:03:45 +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 1tNqu8-00D2zQ-Qm for pgsql-general@arkaria.postgresql.org; Wed, 18 Dec 2024 10:03:44 +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 1tNXq0-001vQA-CO for pgsql-general@lists.postgresql.org; Tue, 17 Dec 2024 13:42:12 +0000 Received: from mail-pg1-x535.google.com ([2607:f8b0:4864:20::535]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tNXpw-000B0B-SW for pgsql-general@postgresql.org; Tue, 17 Dec 2024 13:42:11 +0000 Received: by mail-pg1-x535.google.com with SMTP id 41be03b00d2f7-7feb6871730so3578605a12.2 for ; Tue, 17 Dec 2024 05:42:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1734442927; x=1735047727; darn=postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=fNKlmZPbb2CdGfJbsP6g/yI6XKBORmR8OuueRxFB1sM=; b=lYmMLmU1CORpni1VaOOVPDpOo3XF8V5DrPndFu5ESg2NquUWmNRZN12gnpKDSC//WT Z2RCMcTL4hly1qOSu+1TduEtj3K4ks/l9MvKN92iaa3xZ6JYp0SUznsBsk+vKwEdhA7L AAXozXicEqZN/CPpJDTwsu8WNqKSUt1SYZaAQ+3VCubCDlH3nfmNC5L3/mQyv/ZNjpWY akqkCJnZGSb1qW9BoH1wjuYJBiNJ2VT9LZdKx9Hm2+KxuTdt2HHa4qOcxrGpMBd+ItNX VvFzlis0qJmtVfsesMJ8afq3znzcvqlWFMcmntf6qffcEbr4VYvKFTcqJEGmEu+r6HSi ttxg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1734442927; x=1735047727; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=fNKlmZPbb2CdGfJbsP6g/yI6XKBORmR8OuueRxFB1sM=; b=N9l9RKtXazU1iNba6N6RC8kjyDolyG71Zf/n3/Z4/J3yA+nvHosTIW6xdWa2rnqpb1 uE1M+PWF54vPgDs5SVsXYeDksr3GwHYXsQEWKNcnCyeAxA1KV5VPmfeLrvzNJe2x3kKf atR28kTsEcIzP9EOUcq+GULg4S+JoFfyztUNaaMQNjP5KBsDx6+L3CaDEVgTiC1ZMFoL RKCO22lwFmg8FliF02tDOnm+KoD+E1IUAmUTbUCtcP4spNTMhWekx7LB7WZRqTfDX3BP Yb4QD5ac6QAAra9OuggUsQ5td/XUeqgDjc4MSWVNU7xXoFdjw0Qb+aVE+zYDaKBuz57X 9hbQ== X-Gm-Message-State: AOJu0Yw3eEjmnaoAfs1btlBGHNARTQuJ0l/1yfdu9fySwnR+9QAF+oAP p33DEVjAjRE/fv3zUIppeUJ5nTspM3zSQgHawgLZWdItBZhyRbLd4q28hN/hIt3oXLJJjehUmRr OYFpOWmEVRRN6PjXzOnsRpApeVVA9uiVR/Lw= X-Gm-Gg: ASbGncueYGzqXP5EstUwm3jYn5lT2aZLgTvKJuLkcqnFPpPFUsEZ/7Xvs5GLDtPYkHD b2lS9j05KE8vSw8+MKaHkqn/oFqW1s9jEQTxv X-Google-Smtp-Source: AGHT+IHMDQ19qlnZ1GNVu1J3RYRMG9G8a/37WiI7i8CBS0wW7b2aQpngHW68/t6jUrpYuI760XKeb124FQz39XL7Xak= X-Received: by 2002:a17:90b:3803:b0:2ee:693e:ed7a with SMTP id 98e67ed59e1d1-2f2901b55acmr24749866a91.35.1734442926651; Tue, 17 Dec 2024 05:42:06 -0800 (PST) MIME-Version: 1.0 From: Rama Krishnan Date: Tue, 17 Dec 2024 19:11:55 +0530 Message-ID: Subject: Query about pg_wal directory filled up To: Postgres General Content-Type: multipart/alternative; boundary="00000000000086c254062977767b" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000086c254062977767b Content-Type: text/plain; charset="UTF-8" Hi Team, One of our clients recently migrated from Oracle to PostgreSQL and is conducting multiple scenarios to understand PostgreSQL behavior. One of their main concerns is whether the database will allow `INSERT` queries when the `pg_wal` directory becomes full. As I understand, once the `pg_wal` directory is completely filled, the database will allow only read queries and will not permit any write operations. Kindly advise Thanks RK --00000000000086c254062977767b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Hi Team,

One of our clients recently migrate= d from Oracle to PostgreSQL and is conducting multiple scenarios to underst= and PostgreSQL behavior. =C2=A0

One of their main concerns is whethe= r the database will allow `INSERT` queries when the `pg_wal` directory beco= mes full. =C2=A0

As I understand, once the `pg_wal` directory is com= pletely filled, the database will allow only read queries and will not perm= it any write operations. =C2=A0

Kindly advise


Thanks
RK
--00000000000086c254062977767b--