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 1shpk0-009m0u-Cs for pgsql-general@arkaria.postgresql.org; Sat, 24 Aug 2024 12:19:36 +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 1shpj0-004xqp-CT for pgsql-general@arkaria.postgresql.org; Sat, 24 Aug 2024 12:18:34 +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 1shpiz-004xqg-Vg for pgsql-general@lists.postgresql.org; Sat, 24 Aug 2024 12:18:34 +0000 Received: from mail-yw1-x1132.google.com ([2607:f8b0:4864:20::1132]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1shpiw-001Gfh-9b for pgsql-general@lists.postgresql.org; Sat, 24 Aug 2024 12:18:33 +0000 Received: by mail-yw1-x1132.google.com with SMTP id 00721157ae682-6b8f13f28fbso24638817b3.1 for ; Sat, 24 Aug 2024 05:18:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vlo.city; s=google; t=1724501909; x=1725106709; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=DgHviOAaJr51cmfFGVNrlKARwqdfzKX8snLrJ+8j5Uw=; b=NeNywrH4K9SNc0EFPtDgGsP4cgPaKNvjzkxQ6SUEuRe2FKQKffNV32M0vTEZwK8aOq PkViu1QljAJHah7APexS/CWdD86cNsC0896BvfHE/NJcQnzWlz9L8GNBhph0mgc4Aros mbpZBdL8ch/3p0qnpAuXA06Dzx2eueR+YQ7kf/Ub1nzNgDEQsTgpYqISQD0p4WHj6TcJ vJjDXR2e77ZoyXFvJESJNcbxgKq0u/cUvfNuemM5nS8lBP8LTq9aE9MSoql3wqaOyWxp MoiIr03028AyvQWNkM1BpT6Ham/GkLEWkacZnDUZhPw6DqlMn8A/XRD0NtZ5AaEUFMbP t31Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1724501909; x=1725106709; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=DgHviOAaJr51cmfFGVNrlKARwqdfzKX8snLrJ+8j5Uw=; b=r7zj4K91uspxDvwJqQMwIYnoMxHZ3AQ5hNCrqr48h6i0nGqS8qq7ssP+fHBiID+YUe /WoeN4NkZd7H017KddMf9EFPFP28nLQvbUiohfIbczxrhm6NpSj00/guU1XW6pOCNL+M RDTBE9WGMWlH/Fw98o9yakH7NWggD14noNPHS6ZGDIfPLomSPxOb3I9rerTBlT7VCEQL ippG+sG2avxixPrgkjGEPQ6tFPCtjTGIg2aSJuxfQJ9izt7TPBhF9HyIJ55vDmNtcfds hRJDFYlz4N+z3+KCOIkscb/KigQ7sLwC1X3IhEpTvdwbwQ/Hnesx1HimcymZVU4KR2U0 cdsA== X-Gm-Message-State: AOJu0YwMef+2yxbkSD0FDTbT4GxfR8IgNK9moG+20MCv6nlsFs/iN4TQ 5wzoYvIoIdXAKOHvUWUEzPC6388hTy1xiCsHHrFiIHytyWOAk4uPaPmq+et9tQyF5TECBkzQQVT DzCAD4g0VNfZhwyzPjMLZguOsJ23E9OkMfcdeTkR1xTrE9acmCKk= X-Google-Smtp-Source: AGHT+IFwPe+ql5/8tki+4e+cxRS0Tnl/cmQLvEp7R+OkIjJzs5e0UcjCK0G3ADLwIuq7hKMcL4U9+MnflkKcnrofz5Q= X-Received: by 2002:a05:690c:60c4:b0:66a:7cbe:6d4b with SMTP id 00721157ae682-6c625e277e0mr72254637b3.12.1724501909468; Sat, 24 Aug 2024 05:18:29 -0700 (PDT) MIME-Version: 1.0 From: Manan Kansara Date: Sat, 24 Aug 2024 17:48:19 +0530 Message-ID: Subject: About replication minimal disk space usage To: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000ba913206206ce32f" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000ba913206206ce32f Content-Type: text/plain; charset="UTF-8" Hello All, I have my self hosted postgres server on aws with 16gb disk space attached to it for ml stuff and analysis stuff we are using vertex ai so i have setup live replication of postgres using data stream service to BigQuery table. We use BigQuery table as data warehouse because we have so many different data source so our data analysis and ml can happened at one place. but problem is there When i am starting replication in there pg_wal take whole space about 15.8gb in some days of starting replication *Question *: how can i setup something like that that optimally use disk space so old pg_wal data that are not usable can we delete i think i should create one cron job which taken care whole that things but i don't know any approach can you please guide In future if as data grew i will attached more disk space to that instance but i want to make optimal setup so my whole disk is not in full usage any time and my server crash again. --000000000000ba913206206ce32f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello All,
I have my self=C2=A0hosted postgres server o= n aws with 16gb disk space attached=C2=A0to it for ml stuff and analysis st= uff we are using vertex ai so i have setup live replication of postgres usi= ng data stream service to BigQuery table.=C2=A0 We use BigQuery table as da= ta warehouse because=C2=A0we have so many different data source so our data= analysis and ml can happened=C2=A0at one place.
but problem is there Wh= en i am starting replication in there pg_wal take whole space about 15.8gb = in some days of starting replication=C2=A0

Qu= estion :=C2=A0 how can i setup something like that that opti= mally=C2=A0use disk space so old pg_wal data that are not usable can we del= ete=C2=A0 i think i should create one cron job which taken care whole that = things but i don't know any approach can you please guide
In future = if as data grew i will attached more disk space to that instance but i want= to make optimal setup so my whole disk is not in full usage any time and m= y server crash again.

--000000000000ba913206206ce32f--