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 1t1A7X-00Ezmt-Gn for pgsql-general@arkaria.postgresql.org; Wed, 16 Oct 2024 19:55:47 +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 1t1A7V-009In7-RH for pgsql-general@arkaria.postgresql.org; Wed, 16 Oct 2024 19:55: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 1t1A7V-009Ikz-Fx for pgsql-general@lists.postgresql.org; Wed, 16 Oct 2024 19:55:45 +0000 Received: from mail-oo1-xc2c.google.com ([2607:f8b0:4864:20::c2c]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1t1A7T-001EkR-8F for pgsql-general@lists.postgresql.org; Wed, 16 Oct 2024 19:55:44 +0000 Received: by mail-oo1-xc2c.google.com with SMTP id 006d021491bc7-5e56759e6d7so166301eaf.3 for ; Wed, 16 Oct 2024 12:55:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1729108542; x=1729713342; 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=q/kT10UkqKidBpar2pwy/az7gb+9ju1iX3m/m/b6wkI=; b=geA5nkadDoB0dOjnuSvIiIjgj4yElc9Z3MxRrvIH3UXxR01EIeAJYCHUmzLpeib8uY 6RN8INNoqq8dVI3ilQh2WKFkwZD8nMgKYH84IdVc/FM55Anag2Czgy3S2DSO5dytC26X loOnBeNFdgGKjeDfjs/qRtIoMHfY+pf6WqWb5h5pnLypS5eyX6HgpCRHRqoQqLByMF7w yd/87+DU8xsi5fuFuVK0MIrlQm3Td37C4ZU/Qoa8bnQO7370jU5q/gTBGLxhO2NUyLw9 Yu53bTg73ycrMMzpznbvX3pXeyI36myfyOFcBJ0q9x6A99mPTdKuCAO/KuYZ5FMvQrIT u5fQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1729108542; x=1729713342; 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=q/kT10UkqKidBpar2pwy/az7gb+9ju1iX3m/m/b6wkI=; b=w2KEv8THlUPF1yGwE9I/VplyseeRqPP9iDsGFjePSfGtZJt8M0Mn6ocH2CRCQLN1Pc U5BhwtTxGJnS3SACXM3hYO4YW0cq3bHpixbC/YadsAzmgABb+1YrsD9LpfeRtEnLJH/C IPIxmaWEwXGj7I0XOMi3heVMlJQO6SRGxy7rkQj4dDxcVM02YWVQulkpt50wrE8AEU29 YpEvVdkk9rHKrIp7/mGV5eOUqV0ZLvWnb2Yt5q0mlfAZE/43VKzvs/OOshmeI5whHik4 4p5Xdpi4TURceVOnMLVp3HD8/2gJTgtPvierctayCJopr83elp6bbtVh4JHZfWPfQnKn O/Nw== X-Gm-Message-State: AOJu0Yxu31Co+DM17btbi+McKwGTvOOvv+WM1bP7bOVqQnBcFE9HeurS T9YYda7B9X8yDMjesfVI9tfmp6nDlKuRbQFfObmiJmAogMoyGXa5zGXtK+XAj6ddrCnp3d1McRn 01+FljN0WDyns5Do8u+VFmdSagOy5Zg== X-Google-Smtp-Source: AGHT+IGC7wVhP/nvAwD7JkpLQEBDw8DvMrqq6BX6ef218HHM9fcfHVj2K6bGLy8kzXDCAF19jIBgXGQy0woNDzZYXWU= X-Received: by 2002:a05:6820:54e:b0:5e1:ea03:9286 with SMTP id 006d021491bc7-5eb1a1dc4f2mr12581196eaf.6.1729108542180; Wed, 16 Oct 2024 12:55:42 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Ron Johnson Date: Wed, 16 Oct 2024 15:55:30 -0400 Message-ID: Subject: Re: Backup To: "pgsql-generallists.postgresql.org" Content-Type: multipart/alternative; boundary="0000000000006f55ba06249d74c6" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000006f55ba06249d74c6 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 stor= e > 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. Step 2: show us the "before" df output, the whole pg_dump command, and the "after" df output when it fails. "du -c --max-depth=3D0 $PGDATA/base" also very useful. And tell us what version you're using. --=20 Death to , and butter sauce. Don't boil me, I'm still alive. crustacean! --0000000000006f55ba06249d74c6 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Wed, Oct 16, 2024 at 3:37=E2=80=AFPM A= ndy Hartman <hartman60home@gm= ail.com> wrote:
I am very new to Postgres and have always worked in the mssql wor= ld. I'm looking for suggestions on DB backups. I currently have a DB us= ed to store Historical information that has images it's currently aroun= d 100gig.=C2=A0

I'm looking to take a monthly backup as I archiv= e 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.

S= uggestions on things I can try ?=C2=A0=C2=A0
I did a pg_dump usin= g these parms
--format=3Dt --blobs lobarch

it ran my device out o= f storage:

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

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

looking for the quickest and smallest backup file ou= tput...

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 typ= e.=C2=A0 The data type is what you should use.

Step 2: s= how us the "before" df output, the whole pg_dump command, and the= "after" df output when it fails. "du -c --max-depth=3D0 $PG= DATA/base" also very useful.

And tell us what= version you're using.

--
Death to <Redacted>, and butter sauce.
Don&= #39;t boil me, I'm still alive.
<Redacted> crustacea= n!
--0000000000006f55ba06249d74c6--