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 1t19qG-00EyZZ-6b for pgsql-general@arkaria.postgresql.org; Wed, 16 Oct 2024 19:37:56 +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 1t19qE-0092qA-II for pgsql-general@arkaria.postgresql.org; Wed, 16 Oct 2024 19:37:54 +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 1t19qE-0092ps-3P for pgsql-general@lists.postgresql.org; Wed, 16 Oct 2024 19:37:54 +0000 Received: from mail-yb1-xb31.google.com ([2607:f8b0:4864:20::b31]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1t19qB-001Ed9-Tj for pgsql-general@lists.postgresql.org; Wed, 16 Oct 2024 19:37:53 +0000 Received: by mail-yb1-xb31.google.com with SMTP id 3f1490d57ef6-e28fd8cdfb8so147771276.3 for ; Wed, 16 Oct 2024 12:37:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1729107471; x=1729712271; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=GnBB5HBpq8M5uP5es42wxFBUh1Ua5/Iv9dES2Z2+Vz4=; b=j0cP2b3P5UQ3ATn9PvFIZoJ80eFdHqhDOwIH5w7CCoMRlwe+Yoxl/AWMaoEaAouwfK OM0f+ZnN/miKeLGuRXaKdbnziTfho/Kxafn+SvFP/OOaWLXkG5LGcs6Kt8PH2lR1maBq EkuVP/FW/56imZw/nQyX/ErpBXJRqaxlyg3uB7LjHnjiRRaWTlxqwsUxrfgGI83Dw7oA eQ8uAY4lSI894uALXPNf/k82P3JzelWMjNNvHwgk5OcZZ3iKQkltmU0+k5untdocH+Fr ouwdT7wEAPUv5tWEcdZoiBFpNaKlDWRTHWv4qlVqSbXwMwN+tRqu8iB/ERumP1zLCyd1 LhQQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1729107471; x=1729712271; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=GnBB5HBpq8M5uP5es42wxFBUh1Ua5/Iv9dES2Z2+Vz4=; b=C7KK9QRjh09/Az3jHXg9bebAvTsAPuTo8RtnoyqXahZn1i1DZcaTm4ZjEl4bXHBacI zT2ZBamza1GkBdN4ZhNBEbfpKanxHN56JArGcgxPfkRoDIS8tIxBweOTTgr8pItjV9ye eQUm1WCYiDUE/RbFJ2f8EHv4nA+ddW5+ngrgf0r/+xgjva4/Y+zUJqMliHmKokk9WH4U GDOz9n5ooK2YivJ9qSaMY1p94n6uTVKFUbSY14cZQfmBoB8esbpQ9ks34+79/avO+FEM 1THoBMLedCuSobU3DCa+qfPVsEASYJe8T4Zi8MoRtlpBx2eayiJT79orvIMM1ObioHRu tgDg== X-Gm-Message-State: AOJu0YwerwvTyTdoAjsKQgAe7PW/P4Myfu54hNMm0mWov7se568GRgtw 5loujBKEQmI0INMBl1Y2wfGOtNRMocxcY62Qfph4z6QvYAUTBLSW4x0pqr4FBHh3dpcB5Pp9srf RMW+AiL4I5l+owd3nme+2SbuOxX6DBJ61 X-Google-Smtp-Source: AGHT+IGGdoV4sYvDsSPGovRJGm965tUOCW9U3oR6E6YG3pXCctPmqL9uVoC6JrTZ++PjhBmE0T8tGiyvQbYdmDS926U= X-Received: by 2002:a05:6902:10c7:b0:e29:183f:3d1e with SMTP id 3f1490d57ef6-e297831933bmr4737756276.31.1729107470717; Wed, 16 Oct 2024 12:37:50 -0700 (PDT) MIME-Version: 1.0 From: Andy Hartman Date: Wed, 16 Oct 2024 15:37:39 -0400 Message-ID: Subject: Backup To: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000921f4a06249d34e0" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000921f4a06249d34e0 Content-Type: text/plain; charset="UTF-8" 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 store 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=t --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 --000000000000921f4a06249d34e0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I am very new to Postgre= s 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 loo= king 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=A0c= pu'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 150= gig free on my backup drive... can obviously=C2=A0add more

looking f= or the quickest and smallest backup file output...

Thanks again for = help\suggestions=C2=A0

--000000000000921f4a06249d34e0--