Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1m09jW-0003Kf-E8 for pgsql-admin@arkaria.postgresql.org; Sun, 04 Jul 2021 21:32:58 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1m09jV-0004Op-69 for pgsql-admin@arkaria.postgresql.org; Sun, 04 Jul 2021 21:32:57 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1m09jU-0004Og-RK for pgsql-admin@lists.postgresql.org; Sun, 04 Jul 2021 21:32:56 +0000 Received: from impout007aa.msg.chrl.nc.charter.net ([47.43.20.31] helo=impout007.msg.chrl.nc.charter.net) by makus.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1m09jS-0006qb-Ky for pgsql-admin@postgresql.org; Sun, 04 Jul 2021 21:32:55 +0000 Received: from cerberus.crazybean.net ([71.11.29.254]) by cmsmtp with ESMTP id 09jRmfg1S5d1D09jRmSqb6; Sun, 04 Jul 2021 21:32:53 +0000 Authentication-Results: crazybean.net; none X-Authority-Analysis: v=2.4 cv=eP7WMFl1 c=1 sm=1 tr=0 ts=60e22905 a=GkUsAQdcAzAk0MT19QAIRQ==:117 a=GkUsAQdcAzAk0MT19QAIRQ==:17 a=xqWC_Br6kY4A:10 a=IkcTkHD0fZMA:10 a=e_q4qTt1xDgA:10 a=PRysNqewAAAA:8 a=UnVRJQzzyreoe88AZYwA:9 a=QEXdDO2ut3YA:10 a=Rl1pwT3ZDS7OjzYG58xk:22 Received: from smtpclient.apple ( [2001:470:e117:3:7960:7490:6ffa:4d62]) by cerberus.crazybean.net (OpenSMTPD) with ESMTPSA id f5b8910b (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:NO); Sun, 4 Jul 2021 17:32:46 -0400 (EDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.100.0.2.22\)) Subject: Re: The trap when using pg_dumpall From: Rui DeSousa In-Reply-To: <13043c13-e8ec-bc93-7a50-0da4a15b1431@mailpen.com> Date: Sun, 4 Jul 2021 17:32:46 -0400 Cc: pgsql-admin@postgresql.org Content-Transfer-Encoding: quoted-printable Message-Id: <46651FE6-5D07-44CF-B7D2-3D807EED198F@crazybean.net> References: <24285551-fa0c-0b38-5380-a58aca27a8a9@mailpen.com> <13043c13-e8ec-bc93-7a50-0da4a15b1431@mailpen.com> To: "Dean Gibson (DB Administrator)" X-Mailer: Apple Mail (2.3654.100.0.2.22) X-CMAE-Envelope: MS4xfA59c6JZLG9JDwHVlLIk3cxW+EdgVQllk058duhb5snnPE0TeJAuo7D6bmggHLrhLq/4W1nvEzGAiHxGxOk+FfhL4ZqpLTybg870/nESOPY/Uu7JdBM2 zzS7Aa6BGB2ns+hKIqFy41zvX8UFw3V9WDHCoRTSfd/nnc+sGQg017sJpsdJhDrM0hUMi0/SYx4nZSAnMnK0Kml/wB4pU2oNIuP5myEkMUTv5hvP9VTmsCTv oxZzSSOF8uu/iOeZJ1bkMg== List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On Jul 4, 2021, at 2:04 AM, Dean Gibson (DB Administrator) = wrote: >=20 > Well, I never store the Well, as long as we=E2=80=99re stating I never=E2=80=99s =E2=80=94 let = me state mine; I never consider a logical backup (pg_dump) a proper = backup. They have their use cases and are a very useful tool; however, = I would considered a production database without a physical backup as = not being backed up. Logical backups don=E2=80=99t allow for PITR = recovery and are very slow in comparison. I only use logical backups = for migrations, etc. - more as a tool rather than a backup strategy. A good practice would be to have a separate instance that can = instantiate a point in time recovery. This would allow for the = reviewing/exporting required data needed to resolve a given issue.=