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 1t1AEG-00F0It-G2 for pgsql-general@arkaria.postgresql.org; Wed, 16 Oct 2024 20:02:44 +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 1t1AEE-009WL2-SJ for pgsql-general@arkaria.postgresql.org; Wed, 16 Oct 2024 20:02:43 +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 1t1AEE-009WKb-DI for pgsql-general@lists.postgresql.org; Wed, 16 Oct 2024 20:02:42 +0000 Received: from mail-oo1-xc2b.google.com ([2607:f8b0:4864:20::c2b]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1t1AE8-001Eop-9e for pgsql-general@lists.postgresql.org; Wed, 16 Oct 2024 20:02:41 +0000 Received: by mail-oo1-xc2b.google.com with SMTP id 006d021491bc7-5eb70a772ccso4836eaf.0 for ; Wed, 16 Oct 2024 13:02:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1729108955; x=1729713755; darn=lists.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=3Ug7znjoxl32iG9fFJPitHhUx7G0DXQcerK5Y7vmFUo=; b=EpemxEXMVCsDafuOzauzw0xZX7s2f4g35OIc15nrNxgv24BsuPlJhCXcAaka4mdXH4 7f0+j0cNLLylNPzESMDI0P1aWdXq/DHONesPyqWJ/t62tl8afK3nXXdADR2sYEJoa+B6 YLz0JscYUB8nEwEsQLE5er4KnXrdNW0TqITlWImS39Tsk5eyxWldC3LpPBVKLXT61yUY SqA9dOuWqLd1nkwXCfyc03sJ6sQnFAvyX6M2pa8X9ei2Po1V834FHxQVlkyb51OhJRhL lEi6DiGXwMbl8jbVdsMzM3ZhyBKDiA3x7FWWA5tTXRIUZcgsqRcHsmplUY0ka4qyOst6 4n5w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1729108955; x=1729713755; 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=3Ug7znjoxl32iG9fFJPitHhUx7G0DXQcerK5Y7vmFUo=; b=kZKRAHo9lvJLKxA6B5paSeobXr6pYB9eEli6c7vJfdO4IueF9W9wAzsyj5UbtnC5Uo RRLQ7y8gmjjwslr8oNS/mr8iLy3OH9WCm8zUMaF1KvHCKNfv+w66Xt64dbbk/+XskFS+ ijlxpzMkLU6uhE5t0/JQiG7mE+Tohh2owCqo4VFijy0kJCu5iUHHdsXWtewuN6xt34iv 81VBsJ2s2j4pxIXuieiwPAFAm+Qwl9eMa7pDGU3B39PzwWqV4k/8YiStjdckHU4+56t+ 3PfB3QfOAGA+7Z7bkp8XcRgoVgfYlBMcjNYxN8FiOBrhTelQVjl6/HgmiitbcvkmMGdA REuA== X-Gm-Message-State: AOJu0YxDS+bw84pQ8L+gJDy8iWFWx6MuSvcipYF09dqyfzB5Rp1dPank 4rMnCV4MEtKVDOjHVP85hCfWHrUaJJmiFJ8KZBfsRKIrzSoYwvYNQKDpjWPP3i8jv+z2UwESJCB RN4QzkNkCQ521n88Mi8cgWsgvlP3+SQ== X-Google-Smtp-Source: AGHT+IGMFPCG5p1fWlHkfwSZXyxiIv6IBAbMxvYdK6DbDWzJJxNcnJK+AQmQbY9cb0efseepbrHQM6iOIJgSOwR9wo0= X-Received: by 2002:a05:6820:1628:b0:5e8:3b4:ac22 with SMTP id 006d021491bc7-5eb58c92d0bmr3425627eaf.4.1729108955461; Wed, 16 Oct 2024 13:02:35 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Ron Johnson Date: Wed, 16 Oct 2024 16:02:24 -0400 Message-ID: Subject: Re: Backup To: "pgsql-generallists.postgresql.org" Content-Type: multipart/alternative; boundary="000000000000117ef606249d8d3f" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000117ef606249d8d3f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Oct 16, 2024 at 4:00=E2=80=AFPM Achilleas Mantzios < a.mantzios@cloud.gatewaynet.com> wrote: > =CE=A3=CF=84=CE=B9=CF=82 16/10/24 22:55, =CE=BF/=CE=B7 Ron Johnson =CE=AD= =CE=B3=CF=81=CE=B1=CF=88=CE=B5: > > On Wed, Oct 16, 2024 at 3:37=E2=80=AFPM Andy Hartman > wrote: > >> I am very new to Postgres and have always worked in the mssql world. I'm >> looking for suggestions on DB backups. I currently have a DB used to sto= re >> Historical information that has images it's currently around 100gig. >> >> I'm looking to take a monthly backup as I archive a month of data at a >> time. I am looking for it to be compressed and have a machine that has >> multiple cpu's and ample memory. >> >> Suggestions on things I can try ? >> I did a pg_dump using these parms >> --format=3Dt --blobs lobarch >> >> it ran my device out of storage: >> >> pg_dump: error: could not write to output file: No space left on device >> >> I have 150gig free on my backup drive... can obviously add more >> >> looking for the quickest and smallest backup file output... >> >> Thanks again for help\suggestions >> > > Step 1: redesign your DB to *NOT* use large objects. It's an old, slow > and unmaintained data type. The data type is what you should use. > > You mean bytea I guess. As a side note, (not a fan of LOs), I had the > impression that certain drivers such as the JDBC support streaming for LO= s > but not for bytea? It's been a while I haven't hit the docs tho. > Our database is stuffed with images in bytea fields. The Java application uses JDBC and handles them just fine. --=20 Death to , and butter sauce. Don't boil me, I'm still alive. crustacean! --000000000000117ef606249d8d3f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Wed, Oct 16, 2024 at 4:00=E2=80=AFPM A= chilleas Mantzios <a.= mantzios@cloud.gatewaynet.com> wrote:
=20 =20 =20

=CE=A3=CF=84=CE=B9=CF=82 16/10/24 22:55, =CE=BF/=CE=B7 Ron Johnson =CE=AD=CE=B3=CF=81=CE=B1=CF=88=CE=B5:

=20
On Wed, Oct 16, 2024 at 3:37=E2=80=AFPM Andy Hartm= an <hartman= 60home@gmail.com> wrote:
I am very new to Postgres and have always worked in the mssql world. I'm looking for suggestion= s on DB backups. I currently have a DB used to store Historical information that has images it's currently around 100gig.=C2=A0

I'm looking to take a monthly backup as I archive a month of data at a time. I am looking for it to be compressed and have a machine that has multiple=C2=A0cpu's=C2=A0and ample memory.

Suggestions on things I can try ?=C2=A0=C2=A0
I did a pg_dump using these parms
--format=3Dt --blobs lobarch

it ran my device out of storage:

pg_dump: error: could not write to output file: No space left on device

I have 150gig free on my backup drive... can obviously=C2=A0add more

looking for the quickest and smallest backup file output...

Thanks again for help\suggestions=C2=A0

Step 1: redesign your DB to NOT=C2=A0use large objects.=C2= =A0 It's an old, slow and unmaintained data type.=C2=A0 The data type is wha= t you should use.
You mean bytea I guess. As a side note, (not a fan of LOs), I had the impression that certain drivers such as the JDBC support streaming for LOs but not for bytea? It's been a while I haven'= t hit the docs tho.

Our database is stu= ffed with images in bytea fields.=C2=A0 The Java application uses JDBC and = handles them just fine.
=C2=A0
--
Death to <Redacted>, and butter sauce.
Don't b= oil me, I'm still alive.
<Redacted> crustacean!
--000000000000117ef606249d8d3f--