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 1szKc9-005Vl9-Q5 for pgsql-general@arkaria.postgresql.org; Fri, 11 Oct 2024 18:43:49 +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 1szKc6-009RaR-EL for pgsql-general@arkaria.postgresql.org; Fri, 11 Oct 2024 18:43:46 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1szKc6-009RaJ-2q for pgsql-general@lists.postgresql.org; Fri, 11 Oct 2024 18:43:46 +0000 Received: from mail-pj1-x1033.google.com ([2607:f8b0:4864:20::1033]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1szKc3-000P9D-T2 for pgsql-general@postgresql.org; Fri, 11 Oct 2024 18:43:45 +0000 Received: by mail-pj1-x1033.google.com with SMTP id 98e67ed59e1d1-2e2e87153a3so1114584a91.3 for ; Fri, 11 Oct 2024 11:43:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1728672222; x=1729277022; darn=postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=2TRATznLX8wmMdmEQAl7176ftpLZW7o/BwGx/59Hkgg=; b=k+ZnZ15btFaSUpNF35egGkOaTya91HlSeMbf+wkt0shPusUUueEiHsYaNCYKk15bVr xlPQbKxJEIrs+rR1pIw1xc2SBIlFntyK3mIn5Jjft0kj6Ybt+VRh1YHZwrcvZ0+rBvPe Tuixsp8iNEUsuXsYAmyvj0tg80JKrXPZko/CNB1rwUDSjOwHo0/BQ5+hntRQtrjJ4rSs pyTEfkU7CmAmJzbBprilYqq5gzpq6Ndsw3Kj2KQHqfRQEm9ItSxwwdqk8/fCsSDEFEPj LRKpmFv1UopFf46EDzD88mxXU2dgkjwYnEEDcxWVoBY4cAzH4/Pvl1QxFv8/B/rdHvlX 5oXg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1728672222; x=1729277022; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=2TRATznLX8wmMdmEQAl7176ftpLZW7o/BwGx/59Hkgg=; b=jkk2sbcCJ764hZGcN6mpU/KVkqTA2lBVjGq9JEgwsjyx4KYQhiRvxGjWR8np4Ys8K4 1vg2XZtQ2sQrOwBobGzTbxUY7vHlZo505b94h0ItosRs/TmN7t4h859Asv6vImCKOuQ5 LAcfvuXa1rD3APdO0bIwSHY8ivkY40wwPkL2s4y6V3LI2UzRk97N2Wdmh0X67EPR79J+ guSvL6a67xocVstJ9HQwcKw2VPyv4gEjrkTQH9JemQaWyAFw65dQx6Lr0G2uibLarb4/ Adf1k4xCh87YqnQSVhp4HBUf9WYZ3h0Cl8vy6CCEOdFvTi8g2wiLsS1ZF8M/yYDifPVv HKUA== X-Gm-Message-State: AOJu0YzqZiqi1kYhqsgYK15vnPtyPDD1lQ7oGP3OKgiBPZfArDdBf65d TZDQdg859RR8ktoDkyvsLQ6r+DtqJ39oldYWrhGNP1KNOy+VT168SlgqR4XVkeofBcLDKeL+1Yx Gp0bdm2lupjE97Pk5+3oLa4mMoRGq6hO9 X-Google-Smtp-Source: AGHT+IElkoYIh1apomhdGH/20Yqvl1mZjcMckSzR+GhBU32f3iTfxTPuYQ9o3dXcuCWQpYPbqhORTe6PbGjVK7VGNWo= X-Received: by 2002:a17:90a:644e:b0:2e2:ba35:3574 with SMTP id 98e67ed59e1d1-2e3152ca49bmr496412a91.11.1728672221731; Fri, 11 Oct 2024 11:43:41 -0700 (PDT) MIME-Version: 1.0 From: Kaushal Shriyan Date: Sat, 12 Oct 2024 00:13:30 +0530 Message-ID: Subject: Prune or Purge data stored on Postgres 14.13 To: Postgres General Content-Type: multipart/alternative; boundary="000000000000b5a560062437dda3" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000b5a560062437dda3 Content-Type: text/plain; charset="UTF-8" Hi, I am running PostgreSQL 14.13 on RHEL 8.10 OS. Is there a way to Prune or Purge data stored on PostgreSQL 14.13 ? For example I have Analytics data stored in PostgreSQL 14.13 server for last 1 year (1st September 2023 till date) Is there a way to prune analytics data from Analytics Data stored on PostgreSQL 14.13 Database server starting from 1st September 2023 till February 29, 2024 and archive it to a tape drive or network file storage? (Six months analytics data). This is to make sure we do not run into an out of disk/storage space situation. Once we carry out the prune operation, we only have 6 months of data in the PG Database server and the older data beyond six months will be on tape drive or network file storage. Please guide me. Thanks in advance. Best Regards, Kaushal --000000000000b5a560062437dda3 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

I am running=C2=A0PostgreSQL 14.13 = on RHEL 8.10 OS. Is there a way to=C2=A0Prune or Purge data stored on Postg= reSQL 14.13 ?

For example I have Analytics data st= ored in PostgreSQL 14.13 server for last 1 year (1st September 2023 till da= te)

Is there a way to prune analytics data from Analytics Dat= a stored on PostgreSQL 14.13 Database server starting from 1st September 20= 23 till February 29, 2024 and archive it to a tape drive or network file st= orage? (Six months analytics data). This is to make sure we do not run into= an out of disk/storage space situation. Once we carry out the prune operat= ion, we only have 6 months of data in the PG Database server and the older = data beyond six months will be on tape drive or network file storage.=C2=A0=

Please guide me. Thanks in=C2=A0advance.=C2= =A0

Best Regards,

Kau= shal
--000000000000b5a560062437dda3--