Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1m5QuR-00070e-Aa for pgsql-admin@arkaria.postgresql.org; Mon, 19 Jul 2021 10:54:03 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1m5QuQ-0001KR-A2 for pgsql-admin@arkaria.postgresql.org; Mon, 19 Jul 2021 10:54:02 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1m5QuQ-0001KJ-1A for pgsql-admin@lists.postgresql.org; Mon, 19 Jul 2021 10:54:02 +0000 Received: from mail-wm1-x331.google.com ([2a00:1450:4864:20::331]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1m5QuN-0000pm-PQ for pgsql-admin@postgresql.org; Mon, 19 Jul 2021 10:54:01 +0000 Received: by mail-wm1-x331.google.com with SMTP id y21-20020a7bc1950000b02902161fccabf1so12558503wmi.2 for ; Mon, 19 Jul 2021 03:53:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20150623.gappssmtp.com; s=20150623; h=message-id:subject:from:to:date:in-reply-to:references:user-agent :mime-version:content-transfer-encoding; bh=/kU3rouOhtid5DVz15uaeKGKuPV3jeMUnKERM1dE5FY=; b=M6+n4Prh7FFUBt7SljZdVZnpZ9eUOv2Y50K7PxT80vKAJNMT+sHWqbqRb0RNc022sr JPjvMh5Qu0dJI4LRFKKd4sKQYRwW2+HiD5D/wv32CO0ebsW9QeRb6z7M3IrLPRg7gNMf RS8s4ahLH5k6rwZrtt+mdTPCRGAC3FQNJ6H60r1d//EBNB8KtBE7vvivu2/aXCsLq7jn p2efK4qvrXAN13C9Cyl/LbT4chs/3XDAXchUZG2rA4/610xLC1qyQtsm7xlxHtsihT4v wzLKsiUkB40APbQip6c573N8uEvza++QdinDwovTY0+vIgd6cN2KxRHq4vCSWI1tife/ Y60w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=/kU3rouOhtid5DVz15uaeKGKuPV3jeMUnKERM1dE5FY=; b=lS5sdl3mMms8Tz306t99PNtVVa676ihc7zQRp2LmjKSnpZ4Yv+jVMEzzGMi4+2NByL YGtMLhJvrpd49ryWDbkeU0cm5FGsAqskN9XcyIzTQygC9oY+KA3GVcHvlp2qeI+2FLqt N6vzZ4u3X/4zPUSjYyHEF7QnqT9E9nXzZ5NKY+Qxohj7o0wxdnL7AseKeT9LeFD2sUrB wGNtZXjac6JK1aBiNtbPUDslGgqYueBqyxnAfn3pEqU9jUGU2iS11y+91ZyaiiT87OYr 1q3HtWWo/w+iqR2Iw70R4H3kRm4baFEtr8AEpVXvu8oHG0tdw7PdRsmxgCACiAESCRRU 1jEQ== X-Gm-Message-State: AOAM533ZLhO0rbPYjqw9RQ52LGc4gUqvyrvD4j8akIPtvLk8gLTwMCyJ wuT9KEnG8FTLQ/+ZY0+ugqtShA== X-Google-Smtp-Source: ABdhPJzVXMK0WWNgA75A8HN1heIQhXwj/hZqh+FPTEfTpnGU3oXBYqpWJZjqhQCJl3zaC1WVgE8Uyg== X-Received: by 2002:a7b:c147:: with SMTP id z7mr25618306wmi.110.1626692038525; Mon, 19 Jul 2021 03:53:58 -0700 (PDT) Received: from localhost.localdomain (217-149-171-226.nat.highway.telekom.at. [217.149.171.226]) by smtp.gmail.com with ESMTPSA id p5sm15893780wme.2.2021.07.19.03.53.58 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 19 Jul 2021 03:53:58 -0700 (PDT) Message-ID: Subject: Re: Handling Huge wal files From: Laurenz Albe To: satish v , pgsql-admin@postgresql.org Date: Mon, 19 Jul 2021 12:53:57 +0200 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.36.5 (3.36.5-2.fc32) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, 2021-07-19 at 16:01 +0530, satish v wrote: > we are using the postgresql, we have to table avg 1500 records which stores the documents. > when i am deleting the records of 4 days there are huge number of huge files are generated > and getting the error like 'requested wal files are already removed'. > max_wal_size is 32GB. > How to handle these scenarios. Use a replication slot. Yours, Laurenz Albe -- Cybertec | https://www.cybertec-postgresql.com