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 1tX9hX-004NgE-Jm for pgsql-admin@arkaria.postgresql.org; Mon, 13 Jan 2025 01:57:12 +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 1tX9hV-005Sth-6W for pgsql-admin@arkaria.postgresql.org; Mon, 13 Jan 2025 01:57:09 +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 1tX9hU-005StY-Oa for pgsql-admin@lists.postgresql.org; Mon, 13 Jan 2025 01:57:09 +0000 Received: from mail-oa1-x2f.google.com ([2001:4860:4864:20::2f]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tX9hT-000651-2j for pgsql-admin@postgresql.org; Mon, 13 Jan 2025 01:57:08 +0000 Received: by mail-oa1-x2f.google.com with SMTP id 586e51a60fabf-2a01bcd0143so2603925fac.2 for ; Sun, 12 Jan 2025 17:57:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1736733426; x=1737338226; darn=postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=pNibEWssY7EVw2u7hixC3qqA8DDOAsqtSGkptlqPdBU=; b=Gv8VVSNAdgZhv6NQ6JXC0sUMX5yTbjOt78sn+tadeP4TM6XkNtL42SHbdU3oeeNrem p6dZkU2w080hbmEN6TJx+FVKDAKI6E2dnDVMqZWnyFRAud5Fjn7Tfsd1FWZjuqPUc+7U TK+qc5p2iaYlwnLiQaLwBZi3G7YYl31deT3snRMcGvBquHL6c8FqVAKjhttD6Ce/tkx7 aZFfN0YCPxc4ZfbgmabupKaV0Yss5pKdPGEOU3J53EfehOF/5j+KjmEPX9+idD+jteBQ iyxNNHsL9fYFS9KXw6+i2KQ6DOOu6mSzYEt6EXX5xv3iZ9UMHXDZ0ib5NJ+M4kwCppoH 5nHw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1736733426; x=1737338226; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=pNibEWssY7EVw2u7hixC3qqA8DDOAsqtSGkptlqPdBU=; b=AizsQ9poP3cZ+Xkhr1/9vHUcfG3kduBoii93ZpQz5fdf9bZTc4W8sPbygSOI4P6sqC 9UpVTEWIE1FZs1GONH7CAoZOcOOH7ylhPjtlxMSfE0tVZ+Ov9WHzYfuU615jJcO5OCNh ZY25+3phZ0iAQZMy9J2/sohEtYxWu1BkgA1nkLhXNjPWsLd5gOOJMEN8rU42lzq3z+E3 4NtlwvVEOuSfTTbEatO7mawziuQ2nbysvy+P29GeCxEaBAHdPraE0hWw/cDY1Qa1NkUj y14YyexAthYAP1rDkFoDUPi0d7IMEdaZyVSiiQWZ8xdslXRumP8e4PV1ts/RxRGPaO6J ieCQ== X-Gm-Message-State: AOJu0YykuuELHwCR8u4SQMy2uCdLyPL6R8kF7W2ubHU/IhISuKQWd42B 350kzJUASKP+yKjtboVmB5UhyEu+5vwSe0k8pnAofJirVYnFr+v38UO7x3/v63eeHcQjcqHeQfm A3Mq++di00eDOEpkPvxTRxN6gQU0ZshXI X-Gm-Gg: ASbGncuNzxTCm9PwUV8dqfbRE3Y2SxxuCmnBGhPIlU/g0nGSnGpF7qVIkMn/c/mZjdg oWtvFpqwhRfRDk+Gddr8mNcfaxO7rNHHMSDowofZx4zUqiyQYMTHWTN3akCGfDwhEmK0AjbFM X-Google-Smtp-Source: AGHT+IESA3nGah68CzVJK126gouNM6jrI64R5DiRDozNL9y9IDGjJqk4Z5jnxw+Vgvyj1Gz4o9i3Awa0mtjjDpHk684= X-Received: by 2002:a05:6870:2f0b:b0:29e:5e7b:dc0f with SMTP id 586e51a60fabf-2aa06998858mr10005131fac.38.1736733426313; Sun, 12 Jan 2025 17:57:06 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Ron Johnson Date: Sun, 12 Jan 2025 20:56:55 -0500 X-Gm-Features: AbW1kva2Wp5go569yD5FBNStOtTF33TXZocHxrlncezT6MhdfUARK-IhTbInfsw Message-ID: Subject: Re: Archiving solutions To: pgsql-admin Content-Type: multipart/alternative; boundary="000000000000f1f43c062b8cc25e" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000f1f43c062b8cc25e Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable COPY exists, and is very fast. In my experience, DELETE is quite fast when you: 1. have a supporting index, and 2. don't try to delete too much in one statement. Those are the only PG comments that I needed to archive a 6TB DB down to 2TB. On Sun, Jan 12, 2025 at 3:42=E2=80=AFPM kasem adel w= rote: > Dears , > > Appreciate your support I have 2.4 TB database and I need to implement > archiving solutions to prevent data growthing. > > Thanks > --=20 Death to , and butter sauce. Don't boil me, I'm still alive. lobster! --000000000000f1f43c062b8cc25e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
COPY exists, and is very fast.

In= my=C2=A0experience, DELETE is quite fast when you:
1. have a supportin= g index, and=C2=A0
2. don't try to delete too much in one sta= tement.

Those are the only PG comments that I need= ed to archive a 6TB DB down to 2TB.

On Sun, Jan = 12, 2025 at 3:42=E2=80=AFPM kasem adel <kasemadel8@gmail.com> wrote:
Dears ,

=
Appreciate your support I have 2.4 TB database and = I need to implement archiving solutions to prevent data growthing.=C2=A0

Thanks=C2=A0


--
Death to <Redacted>, and butter sauce.Don't boil me, I'm still alive.
<Redacted> lobs= ter!
--000000000000f1f43c062b8cc25e--