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.96) (envelope-from ) id 1vkSnB-00FfTW-2d for pgsql-general@arkaria.postgresql.org; Mon, 26 Jan 2026 20:02:34 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vkSn9-00AVY2-2h for pgsql-general@arkaria.postgresql.org; Mon, 26 Jan 2026 20:02:32 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vkSn8-00AVXt-2F for pgsql-general@lists.postgresql.org; Mon, 26 Jan 2026 20:02:31 +0000 Received: from fhigh-b1-smtp.messagingengine.com ([202.12.124.152]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1vkSn5-00000000aqJ-2oM9 for pgsql-general@lists.postgresql.org; Mon, 26 Jan 2026 20:02:30 +0000 Received: from phl-compute-05.internal (phl-compute-05.internal [10.202.2.45]) by mailfhigh.stl.internal (Postfix) with ESMTP id A30507A0157; Mon, 26 Jan 2026 15:02:24 -0500 (EST) Received: from phl-frontend-04 ([10.202.2.163]) by phl-compute-05.internal (MEProxy); Mon, 26 Jan 2026 15:02:24 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm1; t=1769457744; x=1769544144; bh=ldMI91z3GSheCuWvwlLr5GN0hgh0fNeAFq2EUKP5i6g=; b= lr++NmuU8qhibbhWdk5t8kALfmpGP7ybZqZMk8yoJoR9RmLrU5YIcfIf59Ad+t9t VZdt/awZCv21IuBXV3SrMBfpXem+EHAe8VpBlMUVVyLGnLhfsQvyub6vL6DT/olu euaihtqXsLlM6fWZXiWXGK3dXo5mOXqs1XDIIQgoZwm1eAKstUMODGSJ/NH37hXs Tq7/6EbTELxY6YuvUNsvhFee4NOu/f3QN4adGwLqCIvMT2M+8M7bam57wxsIJt9z rD07CayBhe+p0zne7gBIG7B+09kl7ZZu5DnE91b/N2/Snz0NLcxyUjALS8VEmnQ+ AFCpbIdgn65vy4lXnW+/CA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; t=1769457744; x=1769544144; bh=l dMI91z3GSheCuWvwlLr5GN0hgh0fNeAFq2EUKP5i6g=; b=WpwiE4XJpHQWJXErG /1RbDAmATkZPuHbXhWnhDdfF9ADwnqtVUZgntiIfs/Z8X9nOqLf0zWd5dOAhMpzL 0SU7WkreJUKPS0xCXKZeLBUx6Vi7RvKvn5NfqzDM2eXPPj/5cI+6wuknsXBBOem4 zdud2BSxvJ1g7KI7UUjfkprPKoCU0pdwF2TWM8EjWJdXO17cJLQVQwW3UVL7xK4M NQS4J9S2HlFAmu9DFneLOFqJL8pJA0EboialGgpxix3u1hgh1EyumDKKYYPh8ScT kDA5GXWA4GXvEEDnTljceaBi8zB5f/AEvS8rCwaziJvhzMioSmJIQInn036B6abo eM4fg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefgedrtddtgdduheekheekucetufdoteggodetrf dotffvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfurfetoffkrfgpnffqhgenuceu rghilhhouhhtmecufedttdenucenucfjughrpefkffggfgfuvfhfhfgjtgfgsehtkeertd dtvdejnecuhfhrohhmpeetughrihgrnhcumfhlrghvvghruceorggurhhirghnrdhklhgr vhgvrhesrghklhgrvhgvrhdrtghomheqnecuggftrfgrthhtvghrnhepffeukefgieeugf dvkeehveejfefffeeiieefkeejgeevgefhieeghffgleefveevnecuffhomhgrihhnpehp ghgsrghrmhgrnhdrohhrghdpphhgsggrtghkrhgvshhtrdhorhhgnecuvehluhhsthgvrh fuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprggurhhirghnrdhklhgrvhgv rhesrghklhgrvhgvrhdrtghomhdpnhgspghrtghpthhtohepvddpmhhouggvpehsmhhtph houhhtpdhrtghpthhtohepfhgvlhhigidrqhhuihhnthhgiieshigrhhhoohdrtghomhdp rhgtphhtthhopehpghhsqhhlqdhgvghnvghrrghlsehlihhsthhsrdhpohhsthhgrhgvsh hqlhdrohhrgh X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 26 Jan 2026 15:02:23 -0500 (EST) Message-ID: <992bfa7f-3a6a-4832-b196-675ec13af754@aklaver.com> Date: Mon, 26 Jan 2026 12:02:23 -0800 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: About backups To: felix.quintgz@yahoo.com, pgsql-general@lists.postgresql.org References: <1730736265.4259921.1769443263077.ref@mail.yahoo.com> <1730736265.4259921.1769443263077@mail.yahoo.com> <868938296.4311067.1769449951678@mail.yahoo.com> <2022327491.4341234.1769452625380@mail.yahoo.com> <32C440DF-84C3-48D3-AF25-C0D977359F56@thebuild.com> <1244937982.4358855.1769455485523@mail.yahoo.com> Content-Language: en-US From: Adrian Klaver In-Reply-To: <1244937982.4358855.1769455485523@mail.yahoo.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 1/26/26 11:24, felix.quintgz@yahoo.com wrote: > A full database backup is the requirement. A database restore is optional, but that's negotiable; the backup is not. > All of this must be done without access to the server or the database itself, solely through the application, and the user must have the necessary permissions within the application. > > The postgresql-client option is probably the right one. FYI, in Postgres 17+ you have in the client program pg_basebackup the option to do incremental backups. In addition there are third party tools that offer more options for backups: https://pgbarman.org/ https://pgbackrest.org/ > I still have the restore history part to do, but the main thing is the backup. > > On Monday, January 26, 2026 at 01:42:55 PM GMT-5, Christophe Pettus wrote: >> On Jan 26, 2026, at 10:37, felix.quintgz@yahoo.com wrote: >> >> I can't change my expectations. It's either you do it or I won't certify you, and you won't be able to use the application. >> That's how a certification body works, and there's nothing I can do about it. > > Can you articulate the specific requirement?  I assume it's not "the database can be backed up completely by issuing an SQL command."  If we know what the precise requirement is, we might be able to provide more specific guidance. > > -- Adrian Klaver adrian.klaver@aklaver.com